Allow suppression of CNFE for interface fields#781
Open
chroniclekevinpowe wants to merge 1 commit into
Open
Conversation
… field, allowing warnings and silent failure.
|
Kudos, SonarCloud Quality Gate passed!
|
peter-lawrey
approved these changes
Dec 6, 2023
Member
peter-lawrey
left a comment
peter-lawrey
left a comment
There was a problem hiding this comment.
Can you change the name of the method to reflect the expected behaviour
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.
When class.not.found.for.missing.class.alias is set to false, no CNFE should be thrown for an interface field set to a missing class name. This allows the user to optionally suppress CNFE behaviour.