-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add feature flags serde_full
and/or decode
#39
Comments
Seems like this is a blocker to using scale on the web and doing any rust in wasm in browser. Maybe I can decode it myself as I now have https://github.com/gilescope/scale-borrow if I impl borrow_decode for the metadata types. I'm guessing there's no metadata metadata... or is there? I'd need scale-info for the metadata types rather than meta-metadata. |
I understand what you mean, however, for the newest metadata it would fairly easy, which would probably cover most of the substrate projects. We did this here: scs/substrate-api-client#259 I was about to suggest an upstream PR for this, but I think I need to have a second look at our feature flags. |
Heart! Yeah am trying that now. So far so good but am still a way off a
real browser…
…On Sat, 16 Jul 2022 at 13:36, clangenb ***@***.***> wrote:
I understand what you mean, however, for the newest metadata it would
fairly easy, which would probably cover most of the substrate projects. We
did this here: scs/substrate-api-client#259
<scs/substrate-api-client#259>
I was about to suggest an upstream PR for this, but I think I need to have
a second look at our feature flags.
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGEJCBM6IPCCKWVCTRW273VUKUGLANCNFSM5ZPE2MBQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Neither
Decode
norDeserializing
are derived inno_std
, which would be very beneficial to us. At a first glance, this should not be a problem with the substrate or scale-info types.Are you open to this?
The text was updated successfully, but these errors were encountered: