We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we only have prettier, which doesn't bring any "code quality" rules, but only opinionated syntax adjustments.
integrate with prettier
unify error/warning for CI/dev: be careful about errors ruining the dev experience
rules:
see if some rules should be kept or not?
cleanup existing rules / disabled rules
The text was updated successfully, but these errors were encountered:
@matthieuh FYI, I created an RFC issue here, so that we add eslint rules to Faency. I don't know if we require a discussion before implem, WDYT?
Sorry, something went wrong.
eslint-disable-next-line @typescript-eslint/no-unused-vars
mdeliatf
Successfully merging a pull request may close this issue.
Goals
Background
Currently we only have prettier, which doesn't bring any "code quality" rules, but only opinionated syntax adjustments.
Description
integrate with prettier
unify error/warning for CI/dev: be careful about errors ruining the dev experience
rules:
see if some rules should be kept or not?
cleanup existing rules / disabled rules
The text was updated successfully, but these errors were encountered: