Allow configuring rename rules for external modules #440
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.
Given cases like #414 , we cannot make the assumption that metadata resolution will always find the appropriate package for a module name.
This PR provides an 'escape hatch' in
external.rename
, a configured list of rename rules to fix external module resolution.For example, if your code uses
pillow
through thePIL
module, butcheck-external
is failing to resolve this, you can add the following config to yourtach.toml
:In general, the
rename
field takes a list of strings in the format[module name]:[package name]
.