API containerwalk-proxies don't actually exist

[corysimmons]

Defined here: https://github.com/shellscape/postcss-values-parser/blob/master/API.md#containerwalk-proxies

Don't exist in codebase: https://github.com/shellscape/postcss-values-parser/search?utf8=%E2%9C%93&q=walkAtWords&type=

[shellscape]

I really do appreciate your interest in the project, and taking the time to open an issue. However, please do dive into the code just a bit more before pulling the trigger on an issue. Those walkers are registered with Container.registerWalker. You can find an example of that here in the Colon class.

There probably should be tests around those, however.

[corysimmons]

Sorry, how do you use it though?

https://github.com/shellscape/postcss-values-parser/blob/master/API.md#containerwalk-proxies could really benefit from a tiny example of usage for those not familiar with proxy functions (like myself). 😬

---

Update: node.type === 'func' is simple enough maybe I'm misunderstanding the purpose of the walker proxies?

[shellscape]

Try walkFunctionNodes. We have a doc discrepancy here due to a reserved word workaround. I also just added some tests confirming the existence of the walkers here. I'll double check the API doc to make sure the function names line up.

As for why they're even there, it was a pattern established by PostCSS that I followed, and they're there as convenience methods for readability as they're a thin layer around walkType.

[corysimmons]

Thanks. Wish there was a gitter so I could harass you for a minute. :D

[shellscape]

Haha well it's bedtime here in the Eastern Time Zone. Feel free to email me and I'll follow up with you tomorrow.