Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| librematch:design:backend:requirements [2022-10-30 23:27] – [User Stories] nimda | librematch:design:backend:requirements [2022-11-04 20:15] (current) – nimda | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| | 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 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 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 | | ||