Feature: ui_preferences field in user profile
- Dominant language
- Python
- Stars
- 26
- Forks
- 28
- Avg merge
- 4h
- Merged PRs (30d)
- 9
Description
Suggested in the forum by @plopluplap_i as part of discussion on [Choix de licence plus facile](https://forum.camptocamp.org/t/choix-de-licence-plus-facile-etait-photos-collaboratives-par-defaut/326430/32) :
> Note : Une amélioration majeure de l’API serait à ce propos un champ libre dans la table profile, nommé ui_preferences, que l’UI utiliserai à sa convenance pour sauvegarder toutes les préférences, et en rajouter des nouvelles sans devoir demander un changement de DB à chaque fois…
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the profile table or model and the API representation used for user profiles. Check how profile fields are validated, stored, and exposed, then determine the expected shape and behavior of ui_preferences. Done means the field can be saved and returned through the API without requiring a schema change for each new UI preference, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100