Temporarily disable pickup slot markers for production release
What does this MR do?
See title. We want to get rid of the pressure of fixing slot markers so we are skipping them for this release. Main reason is they would confuse people with the way they are working right now. There are huge load problems expected with other implementations as it is quite database intensive to calculate them. These problems would add on top of recent unclear/unfixed load problems and would make investigation harder. Pickup markers will be back on beta very soon. Further reasons can be found here #747 (closed) and on many other places :)
How confident are you it won't break things if deployed?
Very
Links to related issues
How to test
Steps a reviewer can take to verify that this MR does what it says it does e.g.
- Checkout branch locally
- Login as store manager
- create empty slots for today/tomorrow
- Login as a foodsaver being part of this store
- Click on the shopping cart
- See: There are no colorful slot markers anymore
Screenshots (if applicable)
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 Chris Oelmueller