Setup Husky for auto formatting on pre commit #854 #859
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
For husky setup I take following steps -:
npm run format
Related Issue
Fixes #856
Motivation and Context
There have been multiple issues while reviewing due to issues with conflicting formats.
Adding Husky to your project to enforce code formatting and linting before commits is a great way to maintain code quality.
How Has This Been Tested?
For Testing husky setup Suppose we have a formatting or linting issue try to commit if Husky blocks the commit due to ESLint issues, review the ESLint output and address the reported issues in your code. Once the issues are resolved, you can attempt the commit again if Husky doesn't block the commit this time and the commit goes through, it means its working fine.
Screenshots or GIF (In case of UI changes):
Types of changes
Checklist: