Invalid status & Single type schema #63
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
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 PR fixes some Bugs which occurred during testing and debugging
1. There was no model rule for the
statusproperty in theWidgetContentmodel.2. Due to Bug 1. the provider for the
statuscolumns in the overview and detail view throw anUndefined array keyif someone set the status to something we do not expect3. JSON Schemas with only one type e.g.:
{"type": "string"}lead to an array which crashes the whole page in which the cell is rendered in. To fix that, we want the properties to always be of type array. Value of a single type schemas are made available via “value”.