a.b || c.dreally.
$.abc) isn't making it into the spec?
@hell-racer , you know @innovate-invent and I are just two guys on the Internet.
You can have a voice.
And the more community members are involved, the better.
We are having quite some heated debates with regards to
Currently, it is being specified as a JEP, as you may have seen, but due to some debate, I feel it cannot be included in the very next immediate short term milestone.
But I would love to have those discussions.
$as the root node is quite handy and is worthy of inclusion.
$to have a more ambitious destiny.
map()we should have
$could play a role, by representing the currently being accumulated value in the reduce operation.
$in the spec repository.
There is some caveat when using functions... Imagine you're accessing a node, and there is no such node. So it just returns
null. But when you use a function, such as
length(), if its argument evaluated to
null it throws an error. So we have to check the node first every time we use
length() or use a fallback in the argument:
abc && length(abc) > `0`
length(abc || ) > `0`
Would it be nice if it just returned
null instead of throwing an error?