Skip to content

Conversation

Myestery
Copy link
Contributor

@Myestery Myestery commented Sep 13, 2024

Description

Issues

Fixes #14564 (comment)
Refs #14564 (comment)

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

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

Myestery and others added 14 commits September 11, 2024 17:42
…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
improve ux for resolving address or name inputs
* add UpdateEmailModal component

* strip attendee specific actions from locks' view

* strip unnwanted metadata and add specific event actions to attendees' view

* linting

* update lock settings metadata card to include email actions
@cla-bot cla-bot bot added the cla-signed label Sep 13, 2024
@Myestery Myestery marked this pull request as ready for review September 13, 2024 15:28
@julien51
Copy link
Member

Thanks!

@Myestery
Copy link
Contributor Author

Looks like we have a nextjs error unrelated to this PR

@julien51
Copy link
Member

ok let's try again then!

@julien51 julien51 merged commit e45d303 into unlock-protocol:master Sep 13, 2024
20 checks passed
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