Users will be able to have configurable settings that should persist.
Implementation
I believe this should be under a new settings table which is tied to the user entity. For now, I think the following schema would be sufficient:
- id
- user_id
- default_ruleset
Objectives
[x] Create settings table that is tied to a user
[x] Create associated service and repository
[ ] Create a settings controller
[x] Allow users to modify their own settings similar to the me controller (the route could even be /me/settings if we want, @myssto let me know your thoughts).
[x] Create endpoint for modifying one's own default ruleset. e.g. PATCH /settings or PATCH /me/settings
User Settings
Users will be able to have configurable settings that should persist.
Implementation
I believe this should be under a new
settingstable which is tied to theuserentity. For now, I think the following schema would be sufficient:Objectives
settingstable that is tied to a usermecontroller (the route could even be/me/settingsif we want, @myssto let me know your thoughts).PATCH /settingsorPATCH /me/settings