fix RemoveImportsVisitor crash when ImportAlias is inserted without comma #397
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
The comment preserving logic introduced in #392 assumed that in an
ImportFrom
node,ImportAlias
es have acomma
property (except for the last one). That's only true if theImportFrom
node is parsed from actual source, but isn't necessarily true if it's constructed manually.This PR adds a defensive check for the existence of a proper
Comma
node, and in case it doesn't exist (because it's aMaybeSentinel
), the logic now just moves over theComma
node from the alias that's about to be removed.Test Plan
Added a test case that adds a new
ImportAlias
node manually (withcomma=MaybeSentinel.DEFAULT
), then removes the next alias.