Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| librematch:design:backend:requirements [2022-10-27 22:51] – ↷ Page moved from librematch:design:requirements to librematch:design:backend:requirements simonsan | librematch:design:backend:requirements [2022-11-04 20:15] (current) – nimda | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| | user | be flexible in the usage of the API | I can take different approaches to find solutions to my problems | | | user | be flexible in the usage of the API | I can take different approaches to find solutions to my problems | | ||
| | user | not over boarded with complexity to use the API | I can start out right away without reading much documentation (reasonable defaults) | | | user | not over boarded with complexity to use the API | I can start out right away without reading much documentation (reasonable defaults) | | ||
| + | | user | be able to query match history for a player by either steam ID or another unique ID | can use the information for calculating statistics, building user facing APIs (eg. !match), build more complicated applications on top of the API | | ||
| + | | user | be able to query information on open/ | ||
| + | | user | be able to query commonly used api strings (for maps, civs, etc.) | can map enum values for maps, civs that are returned by the usual API to names (the api could provide multiple localisations depending on a parameter) | | ||
| + | | user | be able to access typescript type interfaces for api responses | can easily incorporate the API in typescript applications | | ||
| + | | user | be able to query the data of a match that is being cast by a caster | can use it creating a bot to easily modify a casters' | ||
| + | | user | be able to query the data of a match that is being cast by a caster | can compile a list of matches cast by a caster during one stream | | ||