Release 8.0.0 - Support Flow/JSON-Style Nodes

[amihaiemil]

This is a bigger release containing:

Support for reading flow-style nodes (both inline or multiline)! For example:

name: eo-yaml
developers: [amihaiemil, sherif, rultor]
tools: {
  pm: self-xdsd,
  devops: rultor,
  ci: actions
}
empty-map: {}
inline-map: {a: b:, c: d}
empty-seq: []
multiline-sequence: [
  a,
  b,
  c
]

ESCAPING LOGIC FIXES:

Fixes to escaping of strings when printing and reading escaped keys. Previously we would escape any string containing a dash (e.g. kafka-topic: test would be printed as "kafka-topic": test). Now, we only escape it if it starts with a dash (i.e. looks like a block scalar entry). We also do not escape strings containing $ anymore.

Fixes to escaping of scalars containing : - we now only escape the scalar if the value starts with : or if it contains : .* (colon followed by spaces and any characters, indicating a key: value pair.

Small backwards-compatibiliy break: Previously wrongly escaped strings may now be printed as not-escaped, as explained above.

[rocket-3]

@amihaiemil, why issue #368 is not present in the latest release?
Maybe there is some work to be done?
I need that feature and want to contribute, but can't figure out, what to do.

[amihaiemil]

@rocket-3 that's a big feature which is not yet implemented and will require quite some architectural work before actually writing code. Unfortunately I am very busy these days.

You need building/printing or reading, or both?

[amihaiemil]

@rocket-3 actually I see we already started working on this functionality.

I will have a look these days and let you know how we proceed :)

[amihaiemil]

@rocket-3 I will also write a documentation about the architecture.

In principle, the idea of this library is that data is not transformed or mapped. The idea is to not map/transform data or objects, but rather to have different implementations for different scenarios. It's an experiment (which seems to be succesful so far), based on the books "Elegant Objects" and "Object Thinking".

We have for example the YamlMapping with 2 main implementations: BuiltYamlMapping which has a Map behind (this implementation is used when building) and ReadYamlMapping, which is implemented on top of YamlLines which are read from the file (the lines are traversed up and down, left and right, to find the keys and the values).

Now, ReadYamlMapping is actually for block mappings. For flow mappings we need ReadFlow YamlMapping.

[rocket-3]

You need building/printing or reading, or both?

@amihaiemil Printing. Yeah, there's no actual problem reading Flow Mapping as Plain Scalar, ommiting "", but there's no way to skip "" on printing.

[amihaiemil]

@rultor release it please, tag is 8.0.0

[rultor]

@rultor release it please, tag is 8.0.0

@amihaiemil OK, I will release it now. Please check the progress here

[rultor]

@rultor release it please, tag is 8.0.0

@amihaiemil Done! FYI, the full log is here (took me 4min)