Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore TOML support #114

Open
adamziel opened this issue Aug 9, 2024 · 2 comments
Open

Explore TOML support #114

adamziel opened this issue Aug 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@adamziel
Copy link
Collaborator

adamziel commented Aug 9, 2024

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

@adamziel adamziel added the enhancement New feature or request label Aug 9, 2024
@flexseth
Copy link

+1!

Supports

Love the idea of making blueprints more verbose!

@brandonpayton
Copy link
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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants