itowlson
itowlson
Moving the "why" material (or a summary of it?) to the introduction sounds like a good plan. I'm not quite sure what you envisage with splitting up the language guides....
@kate-goldenring I would _really_ not want the first tutorial/introduction to use WAT. That is not going to speak to anyone in the target audience, and for many developers is going...
I'm dubious about this as a _sole_ quick start until there is a sufficient repertoire of off-the-shelf components to make "I will build a thing by composing things from the...
We can, but with a quick start per language, it starts to look like the quick starts are part of the language docs - otherwise the (e.g.) Befunge docs get...
Sounds good - thanks!
@calvinrp Thanks for looking into that. The fix you suggest worked for me (in my one test case!). I haven't explored if it impacts anything else though - @peterhuene do...
This is probably out of scope for this repo - @ricochet are you the right person to determine whether and how to approach this?
I ran into this just the other day! I will try to capture what I did, although it will be Rust-only at this stage.
@chaosprint It might take us a bit to decide on how we want to organise things, but if you want to know about resources pronto, see #140. I'll have a...
Add --format (plain | json) argument to display any output as formatted JSON or plain text (default)
We've got a `--format json` flag on `spin templates list`, and whatever we choose for other commands should be consistent. That said, it's hidden in the UI as it was...