Streamline defining and usage of preferences

[elfjes]

• Render all preferences at page load instead of through ajax requests
• Funnel all preferences update requests through a single view/endpoint
• Introduces a dataclass to hold preference meta information so that this can be stored directly in the Preference class:

@dataclasses.dataclass
class PreferenceField:
    form: forms.Form
    choices: Optional[Sequence] = None
    default: Optional[Any] = None
    partial_response_template: Optional[str] = None

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 64.28571% with 25 lines in your changes missing coverage. Please review.

Project coverage is 80.95%. Comparing base (9aa7f15) to head (3f747a4).

Files with missing lines	Patch %	Lines
src/argus/auth/utils.py	52.38%	10 Missing ⚠️
src/argus/htmx/user/views.py	33.33%	10 Missing ⚠️
src/argus/auth/models.py	83.33%	4 Missing ⚠️
src/argus/auth/context_processors.py	85.71%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1072      +/-   ##
==========================================
- Coverage   81.08%   80.95%   -0.14%     
==========================================
  Files         141      137       -4     
  Lines        5087     5066      -21     
==========================================
- Hits         4125     4101      -24     
- Misses        962      965       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hmpf]

You're assuming all preferences forever will be "select from dropdown".

[elfjes]

Nope, I'm just saying that if they do have choices, you can add them in the PreferenceField directly and they will become available in the rendering context, to be used however the developer sees fit

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud