WIP: Do not store the stores in the session
See: #901 (closed)
What does this MR do?
The list of store menus and their pickup status is not stored in the session anymore, but is loaded on every request.
This way no relogin is required to update the list and no additional cache management is required to update the pickup status.
To reduce the too much load on the server, the query to fetch the pickup states should be optimised as discussed here: https://yunity.slack.com/archives/C1T1ZM9A4/p1572703338028400
Alternatively, we could consider loading the list of stores asynchronously like the baskets and bells.
How confident are you it won't break things if deployed?
Currently, this may have a noticeable effect on the database load.
Links to related issues
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org -
added an entry to CHANGELOG.md (description, merge request link, username(s)) -
Once your MR has been merged, you are responsible to update the #foodsharing-beta Slack channel about what has been changed here. They will test your work in different browsers, roles or other settings
Edited by Johannes