itowlson

@cardoso Lovely to see you again! Thanks for sharing that - I think that might be the v1 manifest, so the `anyOf` stuff might be more containable now - I...

Having a play around with this now. The v2 manifest schema is causing `schemars` some problems, because we use a lot more third-party types (`toml::Table`, `wasm_pkg_common::PackageRef`, etc.), so we're gonna...

Okay there is a "schema so far" at https://gist.github.com/itowlson/030eca82b43bd3f4abc1c3291e159dd4 Even Better TOML users can try it by adding this at the top of a manifest file: ``` #:schema https://gist.githubusercontent.com/itowlson/030eca82b43bd3f4abc1c3291e159dd4/raw/23ae665cc76ba3a8d2d3090a431667a58f0b9bdc/gistfile1.txt ```...

Updated with HTTP and Redis triggers. Auto suggest doesn't feel great in the triggers but errors seem to be redlined and it seems reasonably free of false negatives. ``` #:schema...

We are now generating schemas as part of the release workflow (canary and, in time, official versions), and folks should be able to reference the GH release assets in `#:schema`...

cc @karthik2804

+1 to Radu's second point. We aim to use the _oldest_ Ubuntu image available in GH Actions. Looks like the PR workflow accidentally diverged during a previous iteration.

@rajatjindal You asked for my feedback based on trying to get these working for the SSL stuff. I didn't really do much debugging to be honest: I could not figure...

@rajatjindal Yes. We should: * Use the oldest Ubuntu image available * And use it everywhere

I imagine this would take significant design effort, but my predictive powers would also have ruled out "containers in the browser" and "compile containers to Wasm", both of which have...