Fix Lint issues

[alexanmtz]

When you do a push you will see many lint errors, and we need all those fixes so we can have the push hook green

[alexanmtz]

@KenjxJJ can you work on this?

[KenjxJJ]

Yes.

[effaf]

Hi @alexanmtz , I would like to work on this if there is no resolution yet.

[alexanmtz]

Hello @effaf , there's no resolution yet; feel free to work on it.

[effaf]

Hi @alexanmtz , thank you for assigning the issue. I have a few questions before I get started on this.

1. I ran the command npx eslint --fix . , and could see 104 errors. A lot of these errors were parsing errors due to older eslint version. Can I change the ecmaVersion in the configuration file?
2. Do you want me to comment out the console.log or delete it?
3. A lot of libraries have been imported but not used. Would the maintainers prefer deleting the code or commenting it out?

[alexanmtz]

Hi @alexanmtz , thank you for assigning the issue. I have a few questions before I get started on this.

1. I ran the command npx eslint --fix . , and could see 104 errors. A lot of these errors were parsing errors due to older eslint version. Can I change the ecmaVersion in the configuration file?
2. Do you want me to comment out the console.log or delete it?
3. A lot of libraries have been imported but not used. Would the maintainers prefer deleting the code or commenting it out?

Hey, @effaf, thanks for jumping into this issue and your proactivity. You can change the ecmaVersion in the configuration, and we can eliminate all console.logs except the one with the comment // eslint-disable-next-line no-console

And we can remove the unused libraries.

[alexanmtz]

Hey @effaf, some progress on this one?

[alexanmtz]

There's a bounty of $20 for this one: https://gitpay.me/#/task/840

[guvitorino]

There's a bounty of $20 for this one: https://gitpay.me/#/task/840

I started working on this issue. I saw the comments above and will take them into consideration

[alexanmtz]

That's great @guvitorino, looking forward to review your solution and feel free to change the configuration as suggested before

and fix automatically some issues with npm run lint-fix

[Anshgrover23]

hi i am also doing this

[Anshgrover23]

/attempted Fix Lint issues #1038, plss check @alexanmtz also there is some parsing error were not resolving can u plss check

[Anshgrover23]

/claim #1038

[CodeWithInferno]

/claim #1038

[alexanmtz]

Hello @Anshgrover23 , thanks for sending the PR, I will review in the weekend and when it's merged you can claim the bounty on the web page by going in "Solve issue" and pasting your PR when is merged in "Send Solution" tab

[alexanmtz]

Hey @guvitorino, we have already a PR to review for this one, so let's find another issue for you :)

[Anshgrover23]

@alexanmtz thanks buddy, waiting for your merge reply and thanks for giving me chance

[Anshgrover23]

@alexanmtz made some more commit changes review the pr once again please sir.

[Anshgrover23]

@alexanmtz solved the optonal chaining errors . check new commit

[alexanmtz]

Hey @raviteja83, you fixed this issue successfully; many thanks for the contribution 🚀

You can claim your bounty by visiting this issue on Gitpay: https://gitpay.me/#/profile/task/840/fix-lint-issues

On "Solve Issue" and on the "Send Solution" tab, you can paste the PR merged and the Bounty process will be initiated I hope :)