You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2022. It is now read-only.
Is your enhancement related to a problem? Please describe.
Currently, webpack will not compile the code if eslint fails. I think this isn't necessary since the scaffold already has the precommit hook and based on my experience preventing webpack compilation when eslint fails is a source of confusion.
The precommit hook is a much better place to do those checks and it would act as the last barrier to prevent engineers from pushing code that does not adhere to our eslint.
Additionally, vscode and most IDEs have really good integrations with linting tools and engineers should also be setting those integrations up for a much better experience.
Is your enhancement related to a problem? Please describe.
Currently, webpack will not compile the code if eslint fails. I think this isn't necessary since the scaffold already has the precommit hook and based on my experience preventing webpack compilation when eslint fails is a source of confusion.
The precommit hook is a much better place to do those checks and it would act as the last barrier to prevent engineers from pushing code that does not adhere to our eslint.
Additionally, vscode and most IDEs have really good integrations with linting tools and engineers should also be setting those integrations up for a much better experience.
Describe the solution you'd like
Remove
from webpack.common.js
Designs
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: