But that's more tedious than just parsing the whole thing followed by so some post-parse-processing (which you'd have to do clean up the NULLs anyways).
This would dramatically increase the amount of work that can be done before any R objects materialize and minimize the amount of post-parse-processing a user might have to do in R (and potentially eliminate it for some sane and stable JSON schemata).
The code hygiene and performance benefits are absolutely worth it.
Proposed API:
single queries "recycle" (as they do now: this wouldn't break anyone's code)
the length of multiple queries must match the length json= and are applied in a zip-like fashion
nesting queries inside a list (ListOf<CharacterVector>) like the example above provides a way to apply multiple queries to each element
results of named queries carry the query names (also in example)
We can do better than using a single JSON Pointer for
query=
.If you know exactly what values you want to pull into R, you could do the following:
But that's more tedious than just parsing the whole thing followed by so some post-parse-processing (which you'd have to do clean up the
NULL
s anyways).It's a total waste of potential.
We can do this instead:
This would dramatically increase the amount of work that can be done before any R objects materialize and minimize the amount of post-parse-processing a user might have to do in R (and potentially eliminate it for some sane and stable JSON schemata).
The code hygiene and performance benefits are absolutely worth it.
json=
and are applied in a zip-like fashionListOf<CharacterVector>
) like the example above provides a way to apply multiple queries to each element