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
Please answer the following questions for yourself before submitting an issue.
I am running the latest version
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed
I'm reporting the issue to the correct repository (for multi-repository projects)
Expected Behavior
You have included lint:check and lint:fix in your package.json file, i was expecting there would not have an EsLint issues but i was wrong. There is a lot of linting issues in your theme, if you did not fixed your linting issues i think there is no need to add linting scripts in your package.json
Current Behavior
✖ 489 problems (489 errors, 0 warnings) 5 errors and 0 warnings potentially fixable with the --fix option.
I don't need to manually fix linting issues because its 489 linting errors, which are 484 after run npm run eslint:fix
Failure Information (for bugs)
It's not a bug but i think you should not compromise with quality.
The text was updated successfully, but these errors were encountered:
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
You have included lint:check and lint:fix in your package.json file, i was expecting there would not have an EsLint issues but i was wrong. There is a lot of linting issues in your theme, if you did not fixed your linting issues i think there is no need to add linting scripts in your package.json
Current Behavior
✖ 489 problems (489 errors, 0 warnings) 5 errors and 0 warnings potentially fixable with the
--fixoption.
I don't need to manually fix linting issues because its 489 linting errors, which are 484 after run npm run eslint:fix
Failure Information (for bugs)
It's not a bug but i think you should not compromise with quality.
The text was updated successfully, but these errors were encountered: