Introduces dataType and valueMap to DisplayField
#1747
Merged
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
|
null |
ahennr
approved these changes
Sep 11, 2024
Co-authored-by: André Henn <henn@terrestris.de>
|
🎉 This PR is included in version 8.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
This introduces two new optional properties to the DisplayField:
dataTypeThe
dataTypeallows to force a specific rendering behaviour for the value. e.g.datewill try to transform the value into a moment object which then gets rendered with the specifiedformatproperty:valueMapThe
valueMapallows mapping of values to a new value. This especially useful for enum values. e.g.FINALIZED2024-06-12T08:37:46.057Z