Closed hello-smile6 closed 2 years ago
Your PR will be reviewed over the next 24 hours. Please continue to thoroughly test your code.
I'll try to make a workflow which checks
package.json
for Prettier and fails if it finds it.
this isn't needed nobody will try to use it
however a workflow that checks for syntax errors, thats whats needed. eslint has an option to ONLY check syntax errors instead of styling which breaks everything
I'll try to make a workflow which checks
package.json
for Prettier and fails if it finds it.this isn't needed nobody will try to use it
however a workflow that checks for syntax errors, thats whats needed. eslint has an option to ONLY check syntax errors instead of styling which breaks everything
have eslint not auto fix errors, just LIST them in the PR comments
I'll try to make a workflow which checks
package.json
for Prettier and fails if it finds it.this isn't needed nobody will try to use it however a workflow that checks for syntax errors, thats whats needed. eslint has an option to ONLY check syntax errors instead of styling which breaks everything
have eslint not auto fix errors, just LIST them in the PR comments
Don't know how to do that.
I'll try to make a workflow which checks
package.json
for Prettier and fails if it finds it.this isn't needed nobody will try to use it however a workflow that checks for syntax errors, thats whats needed. eslint has an option to ONLY check syntax errors instead of styling which breaks everything
have eslint not auto fix errors, just LIST them in the PR comments
Don't know how to do that.
Nobody needs eslint if you didn't break this so often
I'll try to make a workflow which checks
package.json
for Prettier and fails if it finds it.