Account for NestedType
in static traversal validation
#31532
Merged
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.
There were a couple locations left which assumed that a schema
Attribute
type was only defined by theType
field, which would end up using an invalidcty.NilType
whenNestedType
was defined. AddImpliedType()
to theAttribute
type which checks for bothType
andNestedType
and use it in place of directType
field references.Leave the
Object.ImpliedType
method for now, sinceobjchange
does specifically split out theNestedType
for validation of optional attributes.Fixes #31527