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

Atom linter for Gherkin #175

Closed
aslakhellesoy opened this Issue Mar 31, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@aslakhellesoy
Copy link
Contributor

aslakhellesoy commented Mar 31, 2017

Summary

Atom linter for Gherkin

Expected Behavior

Open a .feature file in Atom, see linting errors.

Possible Solution

Write a plugin for Atomlinter that uses Gherkin Lint. Since it's all JavaScript, no need to fork a separate process like many other linters do, so it should be fast.

Context & Motivation

Developing this side by side with Gherkin Lint itself would allow us to do Gherkin Lint more "consumer-driven".

@stale

This comment has been minimized.

Copy link

stale bot commented Dec 12, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the Stale label Dec 12, 2017

@stale

This comment has been minimized.

Copy link

stale bot commented Dec 19, 2017

This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective.

@stale stale bot closed this Dec 19, 2017

@lock

This comment has been minimized.

Copy link

lock bot commented Dec 19, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 19, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.