Add TypeToolkit/PreferNotNil cop - #37
Merged
Merged
Conversation
amomchilov
reviewed
Aug 7, 2026
amomchilov
approved these changes
Aug 7, 2026
amomchilov
reviewed
Aug 7, 2026
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
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.
What
Adds an autocorrecting
TypeToolkit/PreferNotNilRuboCop cop that replaces Sorbet'sT.mustwith Type Toolkit's.not_nil!.The cop is enabled by default.
Why
Type Toolkit's
not_nil!provides the same non-nil assertion while producing a more usefulUnexpectedNilErrorwhen the assertion fails. It also supports Core's migration away from runtime Sorbet constructs.Autocorrection details
The autocorrection preserves Ruby semantics and syntax for:
defined?,yield, andsuperT.mustcalls across RuboCop correction passesSplat arguments are not corrected because they do not have a safe receiver-style equivalent.