@passy Unless you actually need it to be un-schematised or need SQL-like I'd suggest just generating some types. See https://t.co/QIijZjlC4c Disclaimer: self-promotion, but there's a reason I made those tools. (You may want the master branch though, I really need to make a new release)
📝 How to win at CORS! Not just how CORS works, but also the history and reasons behind it.
Includes the hot new app everyone's talking about: The CORS playground!
https://t.co/EFGu3JeCq6
@yoshuawuyts Since it looks like the engine source link has disappeared: The code doing the code generation for Rust there is actually Rust code compiled to WASM, and has it's own interface with more options here: https://t.co/jxUbk4LfSP
It's also available as a CLI and proc macro.
@_Francolicious_@thegallowboob For one thing, a lot of people are «blind» to the extent that while they may not have enough vision to read normal text, they can see that there is a view and enjoy that, and have that experience be enhanced by a solution like this.
@mgattozzi@InsanityBit Check out my project, json_typegen. It does types from JSON data at compile time. I have a simplified version in a separate repo, for understanding the algorithm (which was ported from F#).
@Argorak If you are not able to just import and use it is likely due to some strict setting in your tsconfig.json. If I am to hazard a guess I would point noImplicitAny as a likely culprit.
When your @RustFest presentation has some of the nicest slides I have seen it’s a pretty nice detail to throw out there that the presentation is itself a Rust program using the project you are presenting!
@fluffyemily@RustFest@MozillaParis Just left my hotel to go on a search for rustaceans, but have not found any so far. 🦀 Have you arrived in Paris yet?
@ag_dubs@ManishEarth @whoisaldeka @_lbaillie @killercup@rustlang How about Beryl the Borrowing Bird for max alliteration and an oxide reference matching Ferris?