Expand on type of consensus
gregsdennis opened this issue · 2 comments
Currently, consensus is indicated with a simple ✔️. This is misleading when the consensus isn't "returns expected results." For example, Consensus for $[?(@.d in [2, 3])] is that the syntax is not supported, but this still has a ✔️ for many of the libraries.
I think it would be beneficial to have some sort of indicator to show what the consensus is.
(Link to your example https://cburgmer.github.io/json-path-comparison/#filter_expression_with_in_array_of_values).
The most trivial example for the case you describe is probably given with "Parens notation" $(key,more) (https://cburgmer.github.io/json-path-comparison/#parens_notation): One implementation supports it, the rest don't (consensus currently is "NOT SUPPORTED", while some implementations return IMHO a nonsensical response).
What would we want to show here?
I guess the underlying issue here is that "consensus for not supporting a type of query" is treated similarly to "consensus on supporting something". On the former we might want to be more nuanced showing that this type of query is not generally supported, but a small set of implementations exist that suggest a future consensus.