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

no-describe-variables does not work if spec definition is an arrow function #233

Open
plutosimple opened this issue Apr 17, 2020 · 1 comment
Labels

Comments

@plutosimple
Copy link

Describe the bug
The rule 'no-describe-variables' does not work if spec definition is an arrow function.

// Works - error thrown
describe('', function() {
let sampleVar;
}

// Does not work - no error
describe('',() => {
let sampleVar;
}

To Reproduce

  1. Turn the rule on
  2. set a variable under a describe.
  3. The describe should use an arrow function for its spec definition
  4. Run the linter.

Expected behaviour
An error should be shown as 'let sampleVar' is a variable in the describe

Context

  • Node.js version: 10.18.0
  • eslint-plugin-jasmine version: 4.1.0
  • eslint version: 6.8.0
  • Operating system: MacOS Catalina
@lrdiv
Copy link

lrdiv commented Apr 7, 2023

Will this be in an upcoming release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants