Cypress eslint fixes and config#3636
Conversation
f0f3e29 to
5ef1cbe
Compare
|
Looks like codeclimate complies with the root Line 27 in 25910e7 Might have been said here. @arikfr @gabrieldutra wdyt? |
|
Perhaps we can do linting from a CircleCI step instead of CodeClimate? |
|
The issue you linked to mentions:
Maybe we need to remove the explicit eslint config setting and let it find on its own? |
|
lol it worked |
|
I'm gonna test it by pushing a lint error. |
|
No good. There should be 2 errors showing up, but CodeClimate is oblivious @arikfr |
|
It seems to ignore some plugins. |
|
I see 3 ways to go about this:
Gonna try #3 now. |
|
@arikfr so I narrowed it down to a working config:
Good to go? |
| schedule: null, | ||
| }, data); | ||
|
|
||
| // eslint-disable-next-line cypress/no-assigning-return-values |
There was a problem hiding this comment.
cypress/recommended seemed nice 😕. As we can't use it, should those cypress eslint-disable be removed?
There was a problem hiding this comment.
Maybe it's cause the cypress package isn't a required installation.
While I liked the fact you split the configuration, the current version is better than what we had until now so good to go. 👍 |
What type of PR is this?
Description
npm run lintto run on./clientinstead of./client/app.**/distto .eslintignore--ignore-path ./client/.eslintignore. Now there's also no need forlint:stagedspecific folder ignoring.node_modulesfrom ignore file cause it's ignored by default.eslintrcincypressfolder (eslint cascading feature).eslintrc.expect(element).to.be(true)../client/appcause it collided with chai syntax.func-namelint to allow anonymous functionsit('test', function () {.Tested on
npm run lint,lint-stagedand vscode.