Lint git Committed Files & PR Deltas / no-explicit-any

[palisadoes]

We need the ability to selectively adjust our linting rules so that they are eventually applied to our entire code base.

1. Linting rules are managed by the .eslintrc.json file.
2. They are applied to the entire code base at once.
3. If we change a rule from warn to error then every file in the code base will be checked and we have frequently seen our tests fail for dozens of files in hundreds of lines of code.

This is not acceptable.

We have been trying to more strictly lint the entire code base manually, but it has been very slow.

At the user CLI

We need a way to edit .eslintrc.json with increasingly stricter linting rules in such a way that the tests are only applied to the changed files with every git commit and git push command.

These git commands must fail if the linting fails.

With Every Pull Request

We are working on a Talawa-API pull request that checks each submitted file for linting compliance. This can be used as an example of how to run the test against individual files.

• Lint only updated files stricter linting and update the PR workflow talawa-api#1677

You must make sure that this functionality applied for all PRs for this repository whenever the .eslintrc.json file is updated

Other

1. There may be ways to achieve the CLI goals by updating our existing Git Hooks
2. Your solution should preferably work within coding environments such as VScode
3. Please work with @EshaanAgg on this issue

Screenshots

When complete, you should be able to convert all these .eslintrc.json file lines containing warn or off to error and the tests will only be applied to the changed files in git

[AmitSharma512]

@palisadoes can i work on this ??

[skushagra9]

Please assign me @palisadoes

[Pranavx1]

Can i work on this?

[Pranavx1]

Can i work on this?

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

Unassigning due to no activity or PR.

[devsargam]

Hey, can I work on this issue?

[devsargam]

Should I follow similar approach to this for this issue in talawa-admin?
PalisadoesFoundation/talawa-api#1677 (comment)

[palisadoes]

Yes

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigning due to inactivity

[lakshz]

I would like to work on this.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Reopening. It doesn't appear to be linting the deltas in the PR. Please verify and joint the discussion here.

• https://thepalisadoes-dyb6419.slack.com/archives/C06NRV8J9A9/p1711251477990109

[palisadoes]

Closing. The issue was caused by something else