eslint plugin
See original GitHub issueI think we should create a eslint-plugin-cucumber
that adds given
, when
and then
to the environment globals (see https://eslint.org/docs/developer-guide/working-with-plugins#environments-in-plugins), so we don’t need to add /* global given, when, then */
to every step definition file in order to silence the linter.
I don’t know if you’d rather create a separate repo, or host both packages in this one. Either way, if you can get it set up I could work on the code.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Working with Plugins - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >@typescript-eslint/eslint-plugin - npm
@typescript-eslint/eslint-plugin. An ESLint plugin which provides lint rules for TypeScript codebases. NPM Version NPM Downloads.
Read more >ESLint-plugin-jsx-a11y - GitHub
eslint -plugin-jsx-a11y. Static AST checker for accessibility rules on JSX elements. Read this in other languages. Mexican Spanish ...
Read more >eslint-plugin-tsdoc
This ESLint plugin provides a rule for validating that TypeScript doc comments conform to the TSDoc specification. Usage. Configure ESLint for your TypeScript ......
Read more >eslint-plugin-vue: Introduction
Official ESLint plugin for Vue.js. This plugin allows us to check the <template> and <script> of .vue files with ESLint, as well as...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@leegee I’m not sure I understand… Do you want to import cy instead of using it using the one attached to the global context (window)? I would rather have that too - but it’s not really up to us, you would have to ask on https://github.com/cypress-io/cypress - although I doubt they would be willing to do so since mocha already puts a lot of globals for you (describe, test, it, etc).
Understood. Thanks!