Allow to Serialize with line breaks between sections

[emanuel-v-r]

This is related to the issue that I described here #803.
For my usage it's important to be able to serialize a Yaml with line breaks.
Due to yaml's nature, which is declarative and human readable I think it makes sense to support it. We often see files like docker-compose separating sections by break line.
With this PR, that would be possible, either by using YamlMemberAttribute, or by emiting the event manually.
Please let me know if there's an existing and more straightforward way of doing this, then I will abort my PR.
Thanks.

[emanuel-v-r]

@EdwardCooke, would it be possible to get someone to review this?
It would be really helpful.
Thank you.

[JuergenGutsch]

Maybe also related to #523? I will have a look

[emanuel-v-r]

Maybe also related to #523? I will have a look

Actually this is more related to serialization, will update the title and description

[EdwardCooke]

I’ll try and take a look this weekend.

[EdwardCooke]

Sorry for the long delay, was on vacation :) Anyways, what I would prefer is a way of adding any arbitrary content before it, that way it can be whatever is desired by the developer, if we did this as a string, then people could put in whatever the feel like, including something like

something:

# i like
# new lines!

  like: that

  or: just a new line

Also, you'll need to do this on a branch in your fork named something other than master. Using master in your fork breaks the build.

[emanuel-v-r]

No worries, I have mixed feelings about that, I mean it would be more flexible for sure, but at the same time it would allow you to serialize an invalid yaml, while this way it would be more restricted.
Nevertheless if you prefer it that way, I have no issues, it will fit our scenario as well.
Let me know, and I will change the branch and adapt it accordingly

[EdwardCooke]

I’ve been thinking about this more. I really think having the ability to put whatever a person wants in there is a good thing due to flexibility. One idea I have is maybe a check in the attribute setter that makes sure every line is either empty or starts with spaces and/or pound sign. That would guarantee a valid yaml structure at compile time, in theory. I’d like that tested to make sure. But at least it would be validated at runtime at the very least.

[EdwardCooke]

Another issue here is that your branch shouldn't be on master, please create your own, otherwise the build will fail.

[EdwardCooke]

Are you going to create your own, non-master, branch? Or can I close this?

[emanuel-v-r]

I am closing this PR as the approach that you want to follow is a more flexible one and I am not actually sure that those changes are as simple to implement, in the way that I am afraid of users breaking the seriaization/deserialization due to such flexibility.
In fact I am not even thinking on a good use case for this arbitrary string.
Probably that would require more extensive testing as well.