Integrating ESLint and prettier for code quality and consistency #93
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shalithasuranga
approved these changes
Feb 29, 2024
Glad to be able to contribute! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves: #91
This PR integrates ESLint and prettier to our workflow for code quality, consistency and formatting.
This is a common practice in TypeScript projects and it will also ensure the maintainability, readability and cleanliness of the code.
run
npm run formatfor formatting andnpm run lintfor lintingI have added basic settings for now that can be changed as per preference and I didn't run the commands before this PR as it would make the diff very large and make the PR harder to review