return false in Node#walk aborts the entire walk about postcss-values-parser HOT 6 CLOSED

What's the use case? eg. Why would one want to do this?

from postcss-values-parser.

Perhaps I was not clear enough with my example. Consider a rule that is linting the case of keywords, such that they must be lower-case, then I want to examine:

background: url(ToP) TOP left

As soon as I seen the url function I want to stop descending as I don't care the 'ToP' isn't lowercase - however I want to continue parsing the siblings, so I detect 'TOP' as being the wrong case.

from postcss-values-parser.

This isn't something I'm interested in implementing, but I'll accept a PR for review.

from postcss-values-parser.

If I wrote a patch to change return false to mean "abandon this branch" as opposed to "abandon the whole tree" would that be acceptable? Or would it cause too many regressions in downstream use?

from postcss-values-parser.

That's probably a good start, but returning an object with properties to instruct the walker on what course of action to take would probably be more extensible down the road. eg: return { end: 'tree' }; or return { end: 'branch' } or some such.

from postcss-values-parser.

Closing due to age. If anyone would like to open a PR for this we can continue the discussion there.

from postcss-values-parser.