csl.api: Fix wrong @NonNull annotation in methods of Language #8146
+13
−7
Conversation
This file contains 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
The methods: - getOccurrencesFinder - getSemanticAnalyzer - getIndexSearcher - getOverridingMethods can return null, if the implemention does not provide these services. The @nonnull annotation is thus wrong. As Language is not API the use-sites that relied on the non-null assertion were fixed and the annotations updated.
matthiasblaesing
added
CSL
mbien
approved these changes
Jan 15, 2025
|
@mbien thanks |
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.
The methods:
can return null, if the implemention does not provide these services. The @nonnull annotation is thus wrong. As Language is not API the use-sites that relied on the non-null assertion were fixed and the annotations updated.