Closes #17841 Allows Tags to be displayed in specified order #18930
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #17841
Tag.weight
field so users can specify an ordering weight. Valid values are 0-32767.Tag
ordering to('weight', 'name')
so that weights are used for ordering first (lower weights get sorted first) and then names for tie breakers.TaggingMixin.tags
ordering to('weight', 'name')
so that weights are used for ordering first (lower weights get sorted first) and then names for tie breakers. Note: this was required so that calls through an objects.tags
related manager would be sorted when called from a template (e.g. so that ordering would work for things like{% for tag in Tag.objects.all %}
)Tag.weight
in all the required places.