Refactor database access in controllers
Part of #9 (closed)
What does this MR do?
Moves the DB access from some controller classes to gateways. The only controller left is DashboardControl
, which is still worked on in !735 (merged)
How confident are you it won't break things if deployed?
Quite sure. Works locally and in the tests
Links to related issues
Checklist
-
added a test, or explain why one is not needed/possible... same tests as before -
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