Java/C#: Validate all AccessPaths. #12610
Merged
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
michaelnebel
force-pushed
the
java/validatespecs
branch
from
37a7215 to
90dcd1b
Compare
michaelnebel
force-pushed
the
java/validatespecs
branch
from
90dcd1b to
71d184e
Compare
michaelnebel
changed the title
michaelnebel
added
the
no-change-note-required
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.
In this PR we introduce validation for all accesspaths for all Java and C# models.
However, this comes at a cost. Both Java and C# validates Field and Property by checking whether the exist a Field or a Property that matches the accesspath - this validation will no longer be possible, if we want to validate all accesspaths.