Skip to content

Explore TOML support #114

Open
Open

Description

@adamziel

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

Activity

  1. flexseth commented on Aug 10, 2024

    @flexseth

    +1!

    Supports

    Love the idea of making blueprints more verbose!

  2. brandonpayton commented on Aug 12, 2024

    @brandonpayton
    Member

    This sounds like a great idea!

    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?

  3. moved this from Needs Triage/Our Reply to Future work in Playground Boardon Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions