@Peter Huene do you think the encoding/decoding of the metadata JSON custom section belongs in wasm-tools
or registry
?
If it's important enough, I think there could be a case made for it to go in wasm-tools, as the tools do have support for certain well-known custom sections formats (producers, etc)
but if we're talking about it being just a JSON blob, then there's nothing to change really
encoding/decoding will just take the blob and give it back
i don't think we'd want validation in wasm-tools
i'll rephrase: let's not put anything in wasm-tools now, as we can always graduate validation of this data into wasm-tools if it becomes important enough
agreed; most tools won't care about it
from the encoding/decoding side of things, we're already set
my focus the rest of today will be Alex's huge refactoring to WIT to get us IDs :tada: (so long, and thanks for all the URLs)
Made a pr for the registry metadata stuff and saw this thread now. Happy to move it out of tools if you feel it doesn't belong there?
https://github.com/bytecodealliance/wasm-tools/pull/1060
Last updated: Dec 23 2024 at 13:07 UTC