Fix bug where protected types appear as fields in unprotected types #7386
+110
−8
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.
Ref: #7376
This PR fixes a bug reported in #7375 (comment), where a mutation-protected type is incorrectly reported by the linter when it appears as a field of a non-mutation protected type.
This PR improves the logic detecting which fields are allowed to be set to allow this case. It also extends the test cases to include this case.