parseTo takes a string[]... parameter which parses the tokenizer to nested aggregates matching the names given.
For example:
tokenizer.parseTo("a", "b", "c"); will position the tokenizer at the 5.
But would be much better UX to have it like tokenizer.parseTo("a.b.c");.
The biggest issue is that this syntax already matches the current parseTo function. So we need a new name for it.
Ideas:
parseJson
parseExpr
query
parseTotakes astring[]...parameter which parses the tokenizer to nested aggregates matching the names given.For example:
{"a" : {"b": {"c": 5}}}tokenizer.parseTo("a", "b", "c");will position the tokenizer at the5.But would be much better UX to have it like
tokenizer.parseTo("a.b.c");.The biggest issue is that this syntax already matches the current
parseTofunction. So we need a new name for it.Ideas:
parseJsonparseExprquery