Skip to content
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

[BUG] For/Next not recognized if no whitespace after FOR variable #107

Closed
kpowick opened this issue Jun 11, 2020 · 4 comments · Fixed by #108
Closed

[BUG] For/Next not recognized if no whitespace after FOR variable #107

kpowick opened this issue Jun 11, 2020 · 4 comments · Fixed by #108
Assignees
Labels
bug Something isn't working resolved Issue resolved or enhancement added
Milestone

Comments

@kpowick
Copy link
Member

kpowick commented Jun 11, 2020

Describe the bug
This issue was originally reported by @brentlblair as of release of v2.0.7.

A FOR/NEXT statement block displays an error if the variable in the FOR statement has no whitespace between it and the equal sign.

To Reproduce

FOR X = 1 TO 10 <--OK
FOR X=1 TO 10 <-- No whitespace after X. Error displayed by linter

Screen Shot 2020-06-11 at 13 14 19

@kpowick kpowick added the bug Something isn't working label Jun 11, 2020
@kpowick kpowick added this to the v2.0.8 milestone Jun 11, 2020
@kpowick kpowick self-assigned this Jun 11, 2020
@kpowick kpowick changed the title [BUG] For/Next not recognized if no whitespace around equal sign [BUG] For/Next not recognized if no whitespace after FOR variable Jun 11, 2020
@kpowick kpowick added the resolved Issue resolved or enhancement added label Jun 11, 2020
@kpowick
Copy link
Member Author

kpowick commented Jun 11, 2020

@itsxallwater This issue is now resolved on the develop branch. I'll leave it up to you to update master and distribute a hotfix.

If there is anything I can do to help, please let me know.

@itsxallwater itsxallwater linked a pull request Jun 11, 2020 that will close this issue
@itsxallwater
Copy link
Member

We need to get you added to the publisher account in Microsoft but last time we did it for some other folks on the team it was kind of a pain. The good news is building and publishing is pretty straight forward once you're there. I've already done that just buttoning up the repo side.

@kpowick
Copy link
Member Author

kpowick commented Jun 11, 2020

@brentlblair @dthiot I was able to update the extension to v2.0.8 via VS Code, and all is working as expected.

Thanks @itsxallwater for getting this updated version out. I guess 7 wasn't a lucky number for me this time.

@brentlblair
Copy link
Contributor

brentlblair commented Jun 11, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resolved Issue resolved or enhancement added
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants