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.
This is some unplanned work, but that builds on the RPC refactor and a conversation with @fbwoolf and @markmhendrickson.
Currently, we offer RPC types to developers only. With a clean object of known methods, it's fairly straightforward to generate a JS client with methods users can call, which is an improvement on having to access the provider directly from the global object. Parameter and result types are inferred from the RPC spec.
How much we want to expand and maintain this it still in question. Perhaps few will use this, in favour of connect or other wallet wrapping libraries. But, at least in its current bare bones state, it'd be minimal effort to maintain, and might be an interesting package to publish, even if only used for internal use, or docs/demos