Create new DiagnosticGroup for SUSPICIOUS_BREAKING_OUT_OF_OPTIONAL_CHAIN #4222
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.
Discussion on the Closure Compiler Discuss Group: https://groups.google.com/g/closure-compiler-discuss/c/ZpsidQkqdjk
Reasoning for change:
We have set
--jscomp_error suspiciousCode
in our codebase and noticed that we were getting warnings instead of errors forSUSPICIOUS_BREAKING_OUT_OF_OPTIONAL_CHAIN
. We would like this to be an error instead of a warning in line with the otherDiagnosticType
s defined in CheckSuspiciousCode.There are concerns about adding this check to the existing
suspiciousCode
group (see the discussion group thread) so I've created a newDiagnosticGroup
with justSUSPICIOUS_BREAKING_OUT_OF_OPTIONAL_CHAIN
so that it can be configured to be an error.