Improve ESLint Rules #409

[rishitxyz]

fix #409

• added eslint rule to not to use array index as a key for components.
• fixed the components in frontend that created error because of the new eslint rule.

[palashgdev]

also are there only 2 place which require attention ?

[rishitxyz]

also are there only 2 place which require attention ?

Yup, I manually checked files and there were only two files which needed the attention about this new rule. There were a lot of files with map function being used to render components but were not using indices as key.

[palashgdev]

also are there only 2 place which require attention ?

Yup, I manually checked files and there were only two files which needed the attention about this new rule. There were a lot of files with map function being used to render components but were not using indices as key.

use lint command don't check manually

[rishitxyz]

use lint command don't check manually

I even did that too and then manually checked those files.

[rishitxyz]

One of the errors that I am currently having is about line-breaks. I am on a Windows machine and I face this error. We do have an eslint rule about this but that only applies to operating systems based on unix (linux, macOS).

[palashgdev]

One of the errors that I am currently having is about line-breaks. I am on a Windows machine and I face this error. We do have an eslint rule about this but that only applies to operating systems based on unix (linux, macOS).

Yeah agreed we can make a separate issue for this one i guess

do you want to take this one ?

[rishitxyz]

Yeah agreed we can make a separate issue for this one i guess

do you want to take this one ?

I ll be happy to work on this. I will create an issue first and then make a pull request for it once we decide a way to solve the issue.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication