-
Notifications
You must be signed in to change notification settings - Fork 667
kubevirt: add lint scripts #1826
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
kubevirt: add lint scripts #1826
Conversation
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.
I prefer lint:fix.
However recent scripts use lint-fix convention so we should stay aligned.
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.
I decided to leave only lint and one can use lint --fix like in the main package.json
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.
It would be great if we can reuse the script from frontend/package.json via sort of yarn -cwd ../.. lint [TARGET].
Probably a new rule without . directory would need to be defined in the top-level package.json.
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.
good idea, created a #1813 for that so it is possible to lint even from top level
|
Great improvement for development on just |
af830f0 to
9324140
Compare
9324140 to
00d2149
Compare
|
/retest |
1 similar comment
|
/retest |
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.
Nit: please put scripts before dependencies to follow existing convention.
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.
fixed
|
LGTM with minor comment. |
@mareklibra On my machine, it takes even more: $ time yarn lint
yarn run v1.15.2
$ eslint --ext .js,.jsx,.ts,.tsx --color .
...
stuff
...
Done in 80.39s.
real 1m20.884s
user 2m4.998s
sys 0m4.577sThe problem appears to be TypeScript parser for ESLint being slow, which is something we can't impact directly (unless we upgrade to a newer version that has improved performance). |
00d2149 to
67aadcb
Compare
67aadcb to
f817afd
Compare
f817afd to
7f0981b
Compare
|
/test e2e-aws-console-olm |
|
/assign |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: suomiy, vojtechszocs The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
depends on