[CQ] introduce null-safe OpenApi
wrappers
#8139
Open
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.
Currently there are a number of common platform accesses that are not safe, prone to runtime exceptions and spam the inspection log with nullability warnings. This change introduces a host of wrappers around common IntelliJ Open API calls that introduce null-safety, reducing NPE risk, quieting 86 "Nullability and data flow problems" inspections.
Specifically, this change introduces and migrates calls to new
OpenApiUtils
utility methods:safeRunWriteAction
safeInvokeAndWait
safeInvokeLater
getModules
getLibraryTable
getContentRoots
Contribution guidelines:
dart format
.