Forbid RBI outside of configurable AllowedPaths #83
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.
#79
ForbidRBIOutsideOfSorbetDir
makes the assumption that RBI files will always be kept undersorbet/rbi
which is not necessarily the case. See the sorbet docs on RBI files within gems for one example of this. Refactoring the cop a bit allows us to be flexible for these sorts of setups.AllowedPaths will default to
["sorbet/rbi/**"]
to be consistent withForbidRBIOutsideOfSorbetDir
This cop makes no attempts to tell a user where to put things, but allows them to tailor the cop to their needs.
I decided that having AllowedPaths set explicitly to an empty list, nil value, or list containing nil meant it was broken.
See tests for a rundown.