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
Now that we have typescript, linting and code formatting setup for the frontend we should make sure all new code is compatible with the linting, type checking and formatting rules.
Once we add the CI for these actions we won't be able to merge code that's inconsistent with the setup rules, however instead of having to wait for the CI result its better if we run these tools and automatically fix any issues before pushing when creating a commit.
Some of the most standard/popular tools for setting this up on the frontend are lint-staged to only lint staged/edited files instead of the whole project and husky to setup the pre commit hooks
The text was updated successfully, but these errors were encountered:
Now that we have typescript, linting and code formatting setup for the frontend we should make sure all new code is compatible with the linting, type checking and formatting rules.
Once we add the CI for these actions we won't be able to merge code that's inconsistent with the setup rules, however instead of having to wait for the CI result its better if we run these tools and automatically fix any issues before pushing when creating a commit.
Some of the most standard/popular tools for setting this up on the frontend are lint-staged to only lint staged/edited files instead of the whole project and husky to setup the pre commit hooks
The text was updated successfully, but these errors were encountered: