bug: Check for relative import before looking up context.filename #15
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.
If a
--formatargument is passed toReplaceImport, we try and represent it as anImportobject.At this point, we won't have a
context.filenameand will raise an error when trying to normalize a relative import. We don't need to worry about relative imports for imports being passed as--format.This PR moves the relative import check up first so it'll early exit and skip the
context.filenamelookup.