Configurable MaxNumberOfOptions #575 #576
Open
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
rkaldung
added
1 - 🚀 feature
|
@jepf Please check the new system configuration name, the feature looks fine. |
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.
Proposed change
See #575:
When using dynamic fields of type "dropdown" or "multiselect", the default code-setup is that the layout of a select-field (e.g. dynamic field) will be changed when the amount of selectable values is above 1000.
This is for performance reasons, but the limit should be configurable. The layout for fields with >1000 values does not allow searching values and with a configurable maximum number can be set to an individual level to keep the search functionality as long as performance goes along with this.
Type of change
1 - 🚀 feature
Breaking change
Additional information
Checklist