You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JSON is a great data format, but lack of multiline strings can make writing Blueprints in it annoying. TOML seems like a reasonable alternative that supports multiline strings, has a less verbose syntax, and none of the YAML downsides (ambiguity, refs). Perhaps we could easily support both in the medium term?
If we don't have a more intelligent way of discerning between the two, is there any reason we shouldn't try parsing as JSON first and fall back to TOML?
JSON is a great data format, but lack of multiline strings can make writing Blueprints in it annoying. TOML seems like a reasonable alternative that supports multiline strings, has a less verbose syntax, and none of the YAML downsides (ambiguity, refs). Perhaps we could easily support both in the medium term?
cc @dmsnell @brandonpayton @juanmagarrido
The text was updated successfully, but these errors were encountered: