It might be that :a: the behaviour of Selector.all is correct and our assumption was wrong
or :b: Selector.all is wrong and we need to make a breaking change in behaviour.
Or maybe there is a way to add some new all-like primitive that will not allow mixing nesting levels, thus not a breaking change.
fixes #213
So far I've added tests to map this behaviour, of which the interesting one related to #213 fails (L201-214).
It seems
Selector.all [...]
delegates the list back toSelector.Internal.queryAll
, which allows finding the child selector anywhere in the tree.This goes against our assumption in Elm Slack:
It might be that :a: the behaviour of
Selector.all
is correct and our assumption was wrong or :b:Selector.all
is wrong and we need to make a breaking change in behaviour. Or maybe there is a way to add some newall
-like primitive that will not allow mixing nesting levels, thus not a breaking change.