fix: Add default name property to node types defined without a properties key #499
Merged
ali-sedaghatbaf merged 4 commits intomainfrom Mar 31, 2026
Merged
fix: Add default name property to node types defined without a properties key #499ali-sedaghatbaf merged 4 commits intomainfrom
name property to node types defined without a properties key #499ali-sedaghatbaf merged 4 commits intomainfrom
Conversation
ali-sedaghatbaf
changed the title
properties key properties key
ali-sedaghatbaf
changed the title
properties key name property to node types defined without a properties key
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This pull request addresses a validation issue with node type definitions in the schema component. The main improvement is that node types defined without a
propertieskey now automatically receive a defaultname: STRINGproperty andadditional_properties=True, preventing validation errors and matching the behavior for string input. Explicit settings forpropertiesoradditional_propertiesare still respected.Type of Change
Complexity
Complexity: low
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):