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
---
Time: 2001-11-23 15:01:42 -5
User: ed
Warning:
This is an error message
for the log file
---
Time: 2001-11-23 15:02:31 -5
User: ed
Warning:
A slightly different error
message.
...
should result in two different YAML entries. Instead, I end up with:
Which is fine if we're never expecting multiple documents in the same stream, but it can cause problems if we are trying to use it in that fashion. Would you be interested in a patch that adds a new method or a flag for the load methods that causes them to become aware of documents?
I'm not sure if syck handles them or not either, but if they do then this would cause two different behaviours depending on whether or not syck is available.
The text was updated successfully, but these errors were encountered:
I think it's more common for YAML to be used for Front Matter these days, in which everything after the 2nd set of --- hyphens becomes Markdown or another form of text/markup. In that scenario, --- becomes an <hr>. Any solution for streams would have to take that into account as a default behavior.
Hi!
I love using Spyc for YAML parsing, but I have a question - was it intentional not to have multiple document support?
Background: As per http://yaml.org/spec/1.0/#id2489959 YAML streams can have multiple documents. For instance:
should result in two different YAML entries. Instead, I end up with:
Which is fine if we're never expecting multiple documents in the same stream, but it can cause problems if we are trying to use it in that fashion. Would you be interested in a patch that adds a new method or a flag for the load methods that causes them to become aware of documents?
I'm not sure if syck handles them or not either, but if they do then this would cause two different behaviours depending on whether or not syck is available.
The text was updated successfully, but these errors were encountered: