Ryan Levick
Ryan Levick
For almost all of usages of the term "component model", we would likely be better off just saying "WebAssembly components". Usage of the term "component model" naturally leads to the...
As [suggested by @jeffparsons](https://github.com/bytecodealliance/component-docs/pull/1#discussion_r1382331153), we should consider a cookbook section (similar to the likes of [the Rust cookbook](https://rust-lang-nursery.github.io/rust-cookbook/)) that enumerates and shows common tasks that one might want to do...
The idea would be to give short answers to frequently asked questions that then link to other sections of the book where more thorough answers are given. Some example questions:...
The "Why the Component Model" section answers the question of why the component model exists from first principles (i.e., what direct problems of only having wasm modules does the component...
In the [introduction section](https://component-model.bytecodealliance.org/#home) there is a table with the three main sections of the book: "Understanding components", "Building components", "Using components". The use of a table here is fairly...
The following works in the latest release but not on main: ```wit package my-ns:my-package; interface my-interface { my-func: func(); } world my-world { import my-interface; export my-interface; } ``` ```rust...
#296 bumped the minimum supported Rust version (MSRV) to Rust 1.76. I don't believe we document what the MSRV is for cargo-component so I assume it's just the latest version...
Fixes #2607 The database will be selected by the name of the migration file. This makes the name of the migration file significant, whereas previously it was not. If the...
More updates to conformance tests. Now with mqtt tests!
In #1503 we are now ensuring that paths are expanded in expected ways (e.g., environment variable interpolation and `~` expansion). We should be doing the same thing for paths in...