-
Notifications
You must be signed in to change notification settings - Fork 3
Fix 'npm run lint' #46
New issue
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, I think this is a good direction to go into. I have some questions and added some suggestions.
Other than that, please remove all changes from the test folder. We should not change it because a different team is responsible for maintaining it. If you have any specific questions about it, you can ask @navneel99
6d3020c to
2e10e73
Compare
…ckage dependencies in package.json and package-lock.json.
…nd added unused variable handling in createTodo and updateTodo functions.
68aef5b to
ed4eeee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved from my side but let's also wait for a review from @radovanjorgic (and don't forget to test the import with these new changes)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with a comment.
Description
This PR aims to fix the 'npm run lint' command, which runs
eslint .in the background. I've added eslint configuration and fixed all warnings that persisted.DevRev issue
#ISS-185661
Documentation PR
no-docs