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

fix: linter accepts all forms of foreach range #257

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Person-93
Copy link

  • updated positional parser to accespt range specification
  • updated foreach range keyword to use new range spec
  • add PyCharm files to .gitignore
  • mtepfer sign contributor agreement

closes #256

* updated positional parser to accespt range specification
* updated foreach range keyword to use new range spec
* add PyCharm files to .gitignore
* mtepfer sign contributor agreement

closes #256
@Person-93 Person-93 force-pushed the master branch 3 times, most recently from f179735 to a0f0b54 Compare May 23, 2021 12:11
@Person-93
Copy link
Author

I added a commit to fix a security vulnerability, but I forgot that I'd used this branch for a pull request. If you re-run the CI job it should pass like it did before.

@@ -342,6 +342,7 @@ def parse2(cls, ctx, tokens, spec, breakstack):
* "?": zero or one
* "*": zero or more
* "+": one or more
* "min-max": where min is the minimum pargs count and max is the maximum pargs count
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think CI is failing because this line is too long

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Linter only accepts the 3 argument version of foreach's range variant
2 participants