Closed dwsideriusNIST closed 4 years ago
My only question is concerning the
correct_json
function:Since I understand that there will anyhow be another normalization step to postprocess the raw JSON file, the rationale of which fixes are applied in that step vs already in the raw JSON is not clear to me.
After reviewing all of the conversions in correct_json
, we could shift almost everything to postprocessing. All the mappings except for "Select" -> None (null) are available through specific SQL queries to the ISODB tables and those queries can be programmed into new API calls utilized by the JSON postprocessor. So... I'll drastically simplify the pre-output JSON manipulation to just cover the "Select" -> None instances.
That's fine with me
I've cut the correct_json
function and only included the "Select" -> None sanitization. Looks like we have conflicts with master, though!
closing in favor of https://github.com/ltalirz/isotherm-digitizer-panel/pull/53
Updates / Corrections in this PR: