agateblue / agateblue/django-dynamic-preferences

Add optional "ordering" parameter to Section() and BasePreferenceType() for easier

Aperta
#90 2 commenti 3 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Python
Stelle
359
Fork
86
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Right now, both sections and preferences are listed in the order in which they are discovered and loaded into the dynamic preferences registry. However, in a project with multiple apps, it is not always possible to order the apps in `INSTALLED_APPS` so that the sections and individual preferences show up in a sensible order. It is not necessarily desirable to build a form that explicitly orders these preferences, either, since that creates dependencies between otherwise independent apps. Having some more direct control over the display order of both sections and individual preferences would be particularly helpful in these instances.

Default behavior should probably be that preferences without an explicit order value are either displayed last, or (perhaps preferably) are assigned a specific value, so that preferences can be easily ordered to show up either first or last without requiring the ordering to be explicitly defined for each preference. Ties can be broken in the order of discovery, so the existing ordering is preserved in the default situation of no order parameters specified.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.