You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1154 makes subxt-codegen play nicely in WASM. It currently does this by simply hiding all of the jsonrpsee related bits behind a fetch-metadata feature. This feature isn't compatible with the web feature that is also added at the moment.
Since jsonrpsee can be compiled to WASM, we could support fetch-metadata and web together if we wanted.
Secondly, if subxt has its web feature enabled, we should ensure to enable the web feature in subxt-codegen too, just so that subxt-codegen knows to handle this. (easiest way might just be to have a web feature in subxt-macro which jsut enables it in subxt-codegen, and then in subxt we have web = [..., "subxt-macro/web"].
This isn't very pressing, since everything works as-is right now; just a nice to have to consistify things a little.
The text was updated successfully, but these errors were encountered:
#1154 makes
subxt-codegen
play nicely in WASM. It currently does this by simply hiding all of thejsonrpsee
related bits behind afetch-metadata
feature. This feature isn't compatible with theweb
feature that is also added at the moment.Since
jsonrpsee
can be compiled to WASM, we could supportfetch-metadata
andweb
together if we wanted.Secondly, if
subxt
has itsweb
feature enabled, we should ensure to enable theweb
feature insubxt-codegen
too, just so thatsubxt-codegen
knows to handle this. (easiest way might just be to have a web feature insubxt-macro
which jsut enables it insubxt-codegen
, and then insubxt
we haveweb = [..., "subxt-macro/web"]
.This isn't very pressing, since everything works as-is right now; just a nice to have to consistify things a little.
The text was updated successfully, but these errors were encountered: