Use usePublicClient instead of createPublicClient to use the global alchemy api key #80
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
merged since this problem broke the app :/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
So yesterday @Pabl0cks messaged me that address vision did not work. When I got back home and checked, it worked. Few hours after that it stopeed working.
The reason was that I used createPublicClient in some places in the app instead of using usePublicClient which would let us use the alchemy api key set up globally in the app.
This PR
-> Uses usePublicClient instead of createPublicClient wherever possible
-> Adds an alchemy api key to the vercel deployment and uses it
-> Updates an import