Skip to content

Conversation

Myestery
Copy link
Contributor

@Myestery Myestery commented Sep 11, 2024

Description

Ensure consistent eslint rules across all packages, also ensure commands are same and reused in all package.jsons

Issues

Fixes #14564
Refs #14564

Checklist:

  • 1 PR, 1 purpose: my Pull Request applies to a single purpose
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the docs to reflect my changes if applicable
  • I have added tests (and stories for frontend components) that prove my fix is effective or that my feature works
  • I have performed a self-review of my own code
  • If my code involves visual changes, I am adding applicable screenshots to this thread

@cla-bot cla-bot bot added the cla-signed label Sep 11, 2024
@Myestery Myestery changed the title Eslint-cleanup Eslint cleanup Sep 11, 2024
…ummed warning

This commit synchronizes the eslint rules and updates the evm-address-to-checksummed warning. It also fixes the formatting of recipient and userAddress variables to use checksummed addresses.

Fixes unlock-protocol#14592
@Myestery Myestery requested a review from julien51 September 11, 2024 19:11
Copy link
Member

@julien51 julien51 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am genuinely surpirsed that more things are not breaking with all the rules being removed. Were these rules not used at all?

@Myestery
Copy link
Contributor Author

I am genuinely surpirsed that more things are not breaking with all the rules being removed. Were these rules not used at all?

The no-require rule was moved to the base config in the last PR, while some rules were not really used.
A couple of them are still important and exist as seen in the unlock-app package
I believe some of these rules are now part of the default in eslint v9

@Myestery Myestery requested a review from julien51 September 12, 2024 12:23
@julien51
Copy link
Member

ok, one more thing. I see there is at least one duplicated rule between the base and the next config. Can you remove the duplicate from the next config.
Also, can you please check that all rules in base and next are needed and remove them if not?
Thanks!

@Myestery
Copy link
Contributor Author

Hi @julien51 I've been able to sync the rules between the eslint config files and remove unnecessary ones

@julien51
Copy link
Member

Great! Tahnsk a lot!

@julien51 julien51 merged commit 3129cbb into unlock-protocol:master Sep 12, 2024
20 checks passed
julien51 added a commit that referenced this pull request Sep 12, 2024
julien51 added a commit that referenced this pull request Sep 12, 2024
Revert "Eslint cleanup (#14595)"

This reverts commit 3129cbb.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Eslint cleanup
4 participants