fix: import current dir relative modules #1432
Merged
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.
Summary
Attempts to import modules using relative import with multiple module
syntax like
import ./[foo, bar]
no longer result in an error.Fixes: #1430
Details
./some_dir/[foo]
worked because the AST resulted in aninfix
nodefor the second directory separator
/
, but aprefix
node whenusing
./[foo]
,importEval
now takes this into account. A testhas been included along with the fix.
Along with this change some preexisting import statement tests were
adjusted away from using
when false
to flag known issues to thebuiltin testament functionality of the
knownissue
field.