Bump nuget files type strictness
#8468
Merged
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
|
Oh, nice catch @JamieMagee, thanks! |
deivid-rodriguez
approved these changes
Nov 27, 2023
|
Should we be detecting this automatically before merge? |
Yeah maybe we can run |
It might be possible if you were to run EDIT: Jurre beat me to it 😅 |
JINX |
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.
This change bumps the type strictness for the files added in #8179. That PR was started before Sorbet was added to the codebase, so it's expected that they started as
#typed: false.The bump was performed automatically with
bundle exec spoom bump --from=false --to=true nuget.