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

The "Comparison" section doesn't state if there would be any pitfalls to using TOML for data interchange #422

Closed
benrob0329 opened this issue Jun 28, 2016 · 7 comments

Comments

@benrob0329
Copy link

Its probably unnecessary, but Readme.md touches on data exchange, but doesn't state if there if there would be any obvious pitfalls to using it for data exchange program to program.

It could give newcomers (such as myself) a better understanding of usecases if such details were expanded upon.

@a-teammate a-teammate mentioned this issue Oct 14, 2017
26 tasks
@pradyunsg
Copy link
Member

I think we'd be happy to accept a PR for this.

@LucidOne
Copy link

Here are some issues using yaml for embedded data interchange.
yaml/yaml#41

Personally, I think the --- and ... document markers are useful for notifying endpoints that a unit of data is ready for processing without closing a connection. The lack of a header also means data must be identified by something other than magic.

@pradyunsg
Copy link
Member

I welcome PRs for fixing this issue. Please feel free to file a PR and post a comment here if you do. :)

@workingjubilee
Copy link
Contributor

I believe something like #636 is what you were looking for?

@pradyunsg
Copy link
Member

@workingjubilee Yes, almost! :)

@workingjubilee
Copy link
Contributor

Cool, hopefully this wraps that up and answers @benrob0329's question (and also answers a few recurring issues generally?)!

@pradyunsg
Copy link
Member

It does! Thanks @workingjubilee!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants