Skip to content

report: remove eslint --fix step in report generation #13864

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

Merged
merged 2 commits into from
Apr 16, 2022

Conversation

brendankenny
Copy link
Contributor

The time needed for yarn build-report was really a drag today :)

With a few tweaks and eslint-ignoring spacing after commas and double quotes, report/renderer/components.js can still otherwise pass our eslint rules without a call to eslint --fix.

On my machine this drops yarn build-report --standalone down about 45%, to ~2.25s.

@brendankenny brendankenny requested a review from a team as a code owner April 15, 2022 23:09
@brendankenny brendankenny requested review from connorjclark and removed request for a team April 15, 2022 23:09
@@ -4,27 +4,27 @@

/** @typedef {import('./dom.js').DOM} DOM */

/* eslint-disable max-len */
/* eslint-disable max-len, quotes, comma-spacing */
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

but maybe we should just disable eslint entirely?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was originally going to do that but then I saw how few rules were needed. It's nice to have it close to our lint style since it's little effort to get it there. If it ever really needs to diverge it's no big deal to disable, of course.

@brendankenny brendankenny merged commit 2f164ad into master Apr 16, 2022
@brendankenny brendankenny deleted the report-no-fix branch April 16, 2022 00:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants