-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add jest & mocha eslint plugins #207
base: development/8.3
Are you sure you want to change the base?
Conversation
Hello francoisferrand,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
"eslint-plugin-jest": "^28.11.0", | ||
"eslint-plugin-mocha": "^10.5.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to be added to dependencies
(and/or peerDependencies
?) for the plugins to be automatically added to the "top-level" node_modules, and thus available when running eslint...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as we don't need both, they should go in peerDependencies
and eslint should go there too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we don't add it to dependencies
, these plugins will not be included when depending on this plugin (in the "user" package, like cloudserver/...), as peer dependencies do not get installed (just display a warning) : and thus will have more dependencies to include in every package...
The peerDependencies
is not really needed here, what I really want is a dependency : and peerDependency may be added simply to avoid having duplicating versions of the dependency...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But that's the point that we don't want to automatically add it by default, it should be the source repo that picks if it wants to install the plugin jest or mocha based on what it needs to avoid unnecessary dependency.
But maybe they are small enough to ignore an extra unused dependency.
8919c21
to
a5c74e0
Compare
527c61b
to
7c2c026
Compare
Issue: GDL-10
The current config was changed to allow brace-less one-line if, which are not allowed in the guidelines: ``` if (fooo) do_something(); ``` Issue: GDL-10
7c2c026
to
f3725b6
Compare
}, | ||
plugins: ['jest', 'mocha'], | ||
extends: [ | ||
`plugin:${testPlugin}/recommended`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe too strong, causes lots of errors...
→ just "mocha/no-exclusive-tests" and "jest/no-focused-tests" ?
→ or extend recomended plugins, then disable a few (no arrow...)?
Issue: GDL-10