Listbox (multiple) TV: Re-introduce rendering values by selection order #16561
Conversation
This file contains 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
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.
What does it do?
Adds a new input option for this TV type to control the sorting of saved values when rendered to a Resource.
Why is it needed?
A community member requested this functionality be brought back, pointing to possible use cases where preservation of the order of selections made is desirable.
How to test
Create a Listbox (Multiple-Select) TV and experiment with changing the TV behavior via the new Preserve Entry Order option and verify that when this option is set to “Yes,” randomly selected options are shown in the order selected after saving and reloading. Conversely, verify the current default behavior remains intact (i.e., saved values appear in the same order defined by the list itself, no matter the order in which they were selected).
Related issue(s)/PR(s)
Resolves #16495.