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

report column numbers #211

Open
kbirger opened this issue Jan 31, 2020 · 0 comments
Open

report column numbers #211

kbirger opened this issue Jan 31, 2020 · 0 comments

Comments

@kbirger
Copy link

kbirger commented Jan 31, 2020

I am thinking of writing a VS Code extension on top of this package. It would be helpful to have at least a column, but ideally a start and end column reported by the linter. This would allow for precise underlines in VS Code.

In fact, it seems like this might be trivial as rules have access to this information:
https://github.com/vsiakka/gherkin-lint/blob/master/src/rules/indentation.js#L47

Unfortunately, I guess it would be a breaking change.

edit: If this gets support/approval, I would be happy to do the work and submit a PR

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

No branches or pull requests

1 participant