Add new API to receive store meta data
What does this MR do?
Adds a new RestAPI to get information about the store sub-system which needed to be checked by the frontend.
How confident are you it won't break things if deployed?
Nothing
Links to related issues
#1373 (closed) Refactoring of backend with replacement of old XHRMethod in frontend.
How to test
- Login on website (http://127.0.0.1:18080)
- Open restapi (http://127.0.0.1:18080/api/doc/)
- Go to /api/stores/meta-data and execute it
- It provides the maximum allowed count of pickups per slot for all stores.
Screenshots (if applicable)
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) -
added an entry to CHANGELOG.md
- [ ] added a short text that can be used in the release notesNot visible for the typical user -
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing". - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.