itowlson
itowlson
Some not very organised thoughts on this: * There are (at least) three "interesting" operations in Spin - listening, routing and handling. * Listening is a long-running operation that monitors...
A possible handling scenario is presumably the plug-in kind of environment, where the host is the one raising events/commands/queries directly to the plug-in, and doesn't necessarily need routing.
Current behaviour from testing: * Inbound * The original query string is included in `url` * The `params` field is populated * Outbound * If you include a query string...
I will send a PR for 1 and 2.
Slight correction: if you include a query string on an outbound request, _Spin_ leaves it alone. But if you're using the Rust SDK, _that_ strips it out (before passing the...
This behaviour was quite surprising to me - I just spent 20 minutes (and a fair bit of my colleagues' time) trying to figure out why `git fetch upstream` wasn't...
Had an explore of this by allowing a `rename` field with a Liquid template as its value (e.g. `rename = "{{ project-name }}.csproj"`, and that worked okay. However, that approach...
Thanks! Unfortunately, the trouble I'm hitting is not how to do file names in itself; it's extending that to other behaviour overrides. That said, it's cool to see CG doing...
Warning doesn't happen in Rust 1.62.1 but does in 1.63.0.
Also affects programs that import Spin crates, it seems.