Cache clients created from a call to useClients #64
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
When a programmer passes CreateClientArgs to useClients, graz will create a client for the given chain, but will not cache it in the graz store, leading to strange issues where a client has been connected but cannot be retrieved via useClients calls with no arguments. This change stores the clients in the zustand store to avoid such issues.
Checklist
Changes
Testing
To test this, I modified the
example
app to do the following:useClients
call with chain info passed to it to create a client for a locally running chain without having to connect a wallet