Add a json field to the db for all settings that are exclusive for the frontend #1452

Closed
opened 2023-04-01 14:07:00 +00:00 by dpschen · 0 comments
Member

Not sure if we should add a new column for every simple user setting.
Wouldn't it make more sense to have a field that contains a json to join simple settings? Else we need to adjust api / tables for every small persistent setting.

Yes. I think we should add a json field to the db for all settings that are exclusive for the frontend.

Originally posted by @konrad in /vikunja/api/issues/1250#issuecomment-35098

> Not sure if we should add a new column for every simple user setting. Wouldn't it make more sense to have a field that contains a json to join simple settings? Else we need to adjust api / tables for every small persistent setting. Yes. I think we should add a json field to the db for all settings that are exclusive for the frontend. _Originally posted by @konrad in /vikunja/api/issues/1250#issuecomment-35098_
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#1452
No description provided.