Respect custom ordering in metadata#1665
Merged
gregorydlogan merged 1 commit intoopencast:r/19.xfrom Feb 3, 2026
Merged
Conversation
Metadata fields with options (e.g. licenses) can have a custom order specified for their options. The editor did not respect that custom order, but always sorted alphabetically. With this patch, custom orders should be respected.
|
This pull request is deployed at test.editor.opencast.org/1665/2026-01-28_14-36-10/ . |
gregorydlogan
approved these changes
Feb 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #1597.
Metadata fields with options (e.g. licenses) can have a custom order specified for their options. The editor did not respect that custom order, but always sorted alphabetically. With this patch, custom orders should be respected.
How to test this
You'll want to be able to add/change a custom order to/of a metadata field in the Opencast backend. One easy way of doing so is modifying the listprovider file for the licenses: licenses.properties