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

feat(ruleset): introduce parser options #1361

Merged
merged 2 commits into from
Oct 21, 2020
Merged

Conversation

P0lip
Copy link
Contributor

@P0lip P0lip commented Sep 30, 2020

Fixes #1350

Checklist

  • Tests added / updated
  • Docs added / updated

Does this PR introduce a breaking change?

  • Yes
  • No (I believe so? I know we change the default value, but one can easily tune it down if needed)

@P0lip P0lip added the enhancement New feature or request label Sep 30, 2020
@P0lip P0lip self-assigned this Sep 30, 2020
@P0lip P0lip marked this pull request as draft September 30, 2020 15:50
@P0lip P0lip force-pushed the feat/parser-options branch 2 times, most recently from bf07ef1 to fb35ac5 Compare September 30, 2020 15:54
@P0lip P0lip marked this pull request as ready for review September 30, 2020 15:54
@P0lip P0lip force-pushed the feat/parser-options branch 2 times, most recently from 1a73365 to b62c10d Compare October 8, 2020 15:51
@philsturgeon philsturgeon merged commit e7fe8c3 into develop Oct 21, 2020
@philsturgeon philsturgeon deleted the feat/parser-options branch October 21, 2020 16:11
P0lip added a commit that referenced this pull request Nov 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow numeric keys to be classified as errors
2 participants