Remove mandatory condition from the PageTreeRoute path property #7879
Conversation
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
alexander-schranz
approved these changes
Apr 7, 2025
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's in this PR?
In #7842 we introduced an bug for newly created documents with a PageTreeRoute content type. They could not be created anymore, because in the initial state the
pathproperty on the root layer is always missing. As this property was mandatory, the validation always threw an error.Furthermore the PageTreeRoute field type was adjusted, to have
undefinedinstead ofnullvalues, when the selected page is removed. Now the validation works properly and it cannot be saved anymore in this state.Why?
The validation was not working as expected.