Christoph Burgmer
Christoph Burgmer
> We might be able to allow leading digits so that `$.2` is valid. Do note that in the current implementation of Proposal A, `$.2` would only return a value...
I feel we should try to allow all common identifier patterns found across the programming languages that currently implement JSONPath (if that's possible without overlapping with syntax elements too much)....
I've restructured the query names to be more descriptive following a more regular pattern, as laid out in https://github.com/cburgmer/json-path-comparison/blob/master/QUERY_NAMING_PATTERN.md. The latest change now uses that to re-order queries not strictly...
I thought so, but wanted to ask you more about the goal of it. I could envision a table similar to MDN which calls out which browser supports a certain...
Not going to justify the implementation here, just to confirm your observation: Proposal A here parses to the `hasValue` operator, which is implemented by this simple function `(result) => result...
What do you think of https://cburgmer.github.io/json-path-comparison/results/filter_expression_with_equals_boolean_expression_value.html ? Is that comparable? For me what links the queries here is that `true` and `false` can actively be used in the logic, not...
I agree that the constants currently are not helpful, borderline misleading. I created #66 to address that. Let me know what you think please. We would have to make a...
I think I need to process a bit more what you initially wrote @glyn. Apologies that I didn't initial react to that, I think I need some quiet moment to...
Looking at the queries added, there's spotty support for true/false in predicates, and some less intuitive responses as well ("looks buggy"). The more I think about it, the less reasons...
Hey, thanks for checking back. Happy to keep this for a while, as I remember this question coming up before!