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
This is a sibling of #1924. wasm-tools metadata show should print the imports and exports of each component. Unlike the high-fidelity output of wasm-tools component wit, this output would only capture the imported and exported interfaces by name. This is especially interesting when statically composing components, as we'll be able to see just from the metadata which APIs are being virtualized in terms of which others.
Example
For the BA Rust HTTP sample, the cargo component wit output of the component comes in at 299 lines. What we're mainly interested in however is this:
This is a sibling of #1924.
wasm-tools metadata show
should print the imports and exports of each component. Unlike the high-fidelity output ofwasm-tools component wit
, this output would only capture the imported and exported interfaces by name. This is especially interesting when statically composing components, as we'll be able to see just from the metadata which APIs are being virtualized in terms of which others.Example
For the BA Rust HTTP sample, the
cargo component wit
output of the component comes in at 299 lines. What we're mainly interested in however is this:Building on the component output of bytecodealliance/cargo-component#372, I envision us encoding this something like this:
The text was updated successfully, but these errors were encountered: