Add ADR-009 JSON-Suport

[Ozaq]

Description

Contributor Declaration

By opening this pull request, I affirm the following:

• All authors agree to the Contributor License Agreement.
• The code follows the project's coding standards.
• I have performed self-review and added comments where needed.
• I have added or updated tests to verify that my changes are effective and functional.
• I have run all existing tests and confirmed they pass.

[pmaciel]

Excellent study and conclusions. The core advantage is supporting JSON Schema, which will allow a much improved multi-package exchange of information.

I would not weigh the necessity of validating YAML as necessary because at this level the JSON information interchange is certinly adequate, and I see removing YAML at the low level of the stack a good direction (hence I would have finally chosen differently). But this requires a wider agreement and coordination that we're maybe to late to enforce.

The choice is a solid one -- thanks for the hard work!!

[Ozaq]

Excellent study and conclusions. The core advantage is supporting JSON Schema, which will allow a much improved multi-package exchange of information.

I would not weigh the necessity of validating YAML as necessary because at this level the JSON information interchange is certinly adequate, and I see removing YAML at the low level of the stack a good direction (hence I would have finally chosen differently). But this requires a wider agreement and coordination that we're maybe to late to enforce.

The choice is a solid one -- thanks for the hard work!!

We are fully entrenched in YAML, there is so much YAML config. It would a large improvement if we would document the desired YAML structure. Right now we have to pry this knowledge from the code.

[pgeier]

The fact that valijsons adapter architecture allows replacing/adapting any parsing, schema and regex libraries, is a big plus.
JSON, JSON Schema and REGEX is all well defined - the library binds them together. By using a YAML parser we should be able to directly proper error messages - which is a benefit over doing a JSON -> YAML conversion first?
The std::regex is not known to be very performant.

[simondsmart]

Looks well thought through. I would be happy to accept this.

would be

[simondsmart]

Why does it not fit our use case?

[Ozaq]

I believe we also want to be able to write json.

[pmaciel]

Definitely 👍

[marcosbento]

The proposed choice seems to be the most adequate for our purpose.

ecFlow already uses nlohman-json (with the headers embedded into the repo). Once this is accepted, we will gladly adopt it.

[mcocdawc]

Looks very good. My question is only about the proposed example usage.