Use the JSON lib to generate call end data #927
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.
Instead of using file operations to emulate the creation of call JSON, this should be handled by the new JSON library. This should ultimately be easier to maintain, less prone to typo errors, and provide easier-to-read output.
Upon call completion, the call information is first collected into an
ordered_json
object before being written to disk with two-space indentation.This json object is now included in the
Call_Data_t
struct, and passed back tocall_info
after generation. Doing so allows upload plugins to have direct access to this call end data without re-reading the .json file, or including a redundant method to recreate it locally.