Stanisław Barzowski

@morlay Yes, I think this is a promising direction. It allows us to start describing types without any immediate change to the language. Once we have a more concrete schema...

Cool stuff! Thank you both for exploring this area! > If you and JSONNET community accept this way, we could make it as built-in. Supporting the official JSON Schema validation...

You're right, this is different. Choosing which strings to quote in YAML is a tricky issue. See the famous [Norway Problem](https://medium.com/@lefloh/lessons-learned-about-yaml-and-norway-13ba26df680). If you could find a comprehensive set of rules...

No, this is not safe. Consider the following YAML: ``` no: 42 ``` It is canonicalized to the following JSON: ``` { "false": 42 } ``` Try it in https://yaml-online-parser.appspot.com/....

Not really. We want all the behavior to be well-defined and the best way to ensure that is to have reference implementation in Jsonnet whenever possible. In principle everyone should...

> Hopefully the work could be limited somewhat by considering only keys (not values), as @grosser suggested. I'm afraid it doesn't help much. Per YAML spec 7.4.2: "Note that YAML...

Some related work: https://github.com/databricks/sjsonnet/pull/90. If we could this sort of processing as a Jsonnet library it would be a first step here.

hmm... perhaps instead of REPL for exploration we can recommend that they edit a file and have it automatically executed? In the simplest version it can be achieved with a...

The main issue with repl is that, because Jsonnet is a functional, expression-oriented language, so your every entry in repl would basically need to be a separate program. I think...

We're happy to go forward if the PR author (or someone else) is willing to pick this up again and fix the build issues.