-
Notifications
You must be signed in to change notification settings - Fork 699
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
Add prefer-const linting rule to kolibri-tools #10130
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.
Thank you for your contribution, @Akila-I. Code changes are looking good to me.
There's one more step that is needed to fix the codebase and that is running npm run lint-frontend:format
(automatical fix) and then committing all remaining files (those will be files that didn't need manual fix). I think this should also solve the failing linting check on this pull request.
And just a side note, there's no need to be concerned about the "Kolibri Build Assets for Pull Request / Build DMG file / build_dmg (pull_request) " failing check, it's not related to this PR |
Hi @MisRob , changes you requested are made and pushed. |
@Akila-I Thank you,I'll have a look soon |
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.
All changes look correct here!
Please feel free to push another commit here, or add a follow up PR adding yourself to the AUTHORS.md file.
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.
Thanks for the updates @Akila-I and for reviewing @rtibbles. I briefly skimmed through the most recent force push and haven't noticed anything suspicious, so I think it's ready for merge. I will wait for @rtibbles to do so because I'm not sure what would be the best timing in regard to one of his linting PRs.
Thanks for the guidance and quick responses @MisRob, If this issue is finished, would love to take part in another contribution. Any suggestions of issues? |
Summary
npm run lint-frontend
. No errors found.References
Reviewer guidance
npm run lint-frontend
to check ESLint rules compliance.Testing checklist
PR process
Reviewer checklist
yarn
andpip
)