agateblue / agateblue/django-dynamic-preferences

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

Ouverte
#90 2 commentaires 3 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
359
Forks
86
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.