Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use unexistent exportation from upgrade module #6228

Merged
merged 2 commits into from
Feb 21, 2025

Conversation

EnThib
Copy link
Contributor

@EnThib EnThib commented Feb 5, 2025

  • Because this PR includes a bug fix, relevant tests have been included.
  • Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
  • I didn't do anything of this.

It's not much but it can cause confusion in the documentation. Above the documentation makes us export the "DemoModule" and here we use "useModule" with the proxy module which is not supposed to be exported, I therefore deduce that we must use the import which was introduced above.

Thank you for taking the time to read me and have a good day.

Copy link

changeset-bot bot commented Feb 5, 2025

⚠️ No Changeset found

Latest commit: 5761175

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Feb 5, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hardhat ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 19, 2025 7:35am

@alcuadrado
Copy link
Member

I think this change makes sense. Can you double check it, @zoeyTM ?

Also, I think there's another mention of proxyModule a bit below.

@alcuadrado alcuadrado added the no changeset needed This PR doesn't require a changeset label Feb 5, 2025
@zoeyTM
Copy link
Contributor

zoeyTM commented Feb 6, 2025

Yep, this looks right, good catch! There are a couple more references to this mistake that should be fixed on lines 315, 323, 356, 364, and 394. If you would correct those as well then we can get this merged @EnThib

Copy link
Contributor

@zoeyTM zoeyTM left a comment

Choose a reason for hiding this comment

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

see my comment above ^ this looks good though!

@EnThib
Copy link
Contributor Author

EnThib commented Feb 6, 2025

@zoeyTM It's done :)

Copy link
Contributor

@zoeyTM zoeyTM left a comment

Choose a reason for hiding this comment

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

LGTM!

@zoeyTM zoeyTM merged commit 504074c into NomicFoundation:main Feb 21, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no changeset needed This PR doesn't require a changeset status:triaging
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants