You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
This repository is pretty outdated and not maintained anymore.
How about replace it by https://github.com/funkwerk/gherkin_lint?
It's also in ruby and it implements nearly everything mentioned in README.md.
I would agree to delete it from funkwerk/gherkin_lint and publish it under cucumber-ltd.
Should I do a PR for it?
The text was updated successfully, but these errors were encountered:
After a discussion in cucumber/common#59 I made a decision to start an official Gherkin-Lint in the Cucumber monorepo. It currently lives on the gherkin-lint branch. It hasn't been very active yet because we decided to do some work in Gherkin first, that will make it easier to implement a linter.
The plan is to use the Cucumber Event Protocol and the new Stream API (cucumber/gherkin#240) that will be part of the next Gherkin release. The official Gherkin-Lint will be written in JavaScript.
there is already an example rule implemented, that means other rules could be implemented in a similar way?
What would be the next steps?
Should I PR for a next linter-rule?
Or should we first agree on a list of lints to support?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This repository is pretty outdated and not maintained anymore.
How about replace it by https://github.com/funkwerk/gherkin_lint?
It's also in ruby and it implements nearly everything mentioned in README.md.
I would agree to delete it from funkwerk/gherkin_lint and publish it under cucumber-ltd.
Should I do a PR for it?
The text was updated successfully, but these errors were encountered: