Add support for conversion to JSON #312
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BEGINRELEASENOTES
PODIO_JSON_OUTPUT
and to link against the nlohmann/json library.ENDRELEASENOTES
Inspired by the brief discussion in key4hep/EDM4hep#163
This makes it possible to convert objects and collections into JSON by generating a
to_json
function that is necessary for serialization of arbitrary types in the nlohmann/json library (see documentation).Converting a collection to JSON is as simple as
Each element of the collection will be converted to a JSON object, where the keys are the same as in the datamodel definition file. Relations are stored as objects with a 'collectionID' and 'index' key for each relation.