-
Notifications
You must be signed in to change notification settings - Fork 219
fixes match statements to work with PositionProvider #1369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fixes match statements to work with PositionProvider #1369
Conversation
|
Hi @patreon-steve! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
|
Hi @patreon-steve, However there are a few failing tests, it seems like the python parser doesn't support match statements.
|
Awesome. Thank you |
|
Hi @drinkmorewaterr. I wonder if there is any updates here. I'd like to use "match" statements and make libCST work with it. Thank you! |
|
Hi @patreon-steve, |
|
I'm taking over this fix from @patreon-steve. The new PR here #1389 |
Summary
Fixes issue 1322 where
PositionProviderdoes not provide positions for whitespace. The issue seems to be that when there is no pattern for whitespace nodes during codegen, then they are not included in the position metadata.Test Plan