Documentation and Code Quality
As the above StackExchange answer attests to, I finally know what the
registry is for. If you’ve got a view model, it lets you figure out which nodes that model is bound to via the
Part of the reason it was so hard to get an answer or figure this out myself? The module doesn’t work as intended. It’s got a bug (as outlined in this community thread) that makes the module not work as intended.
It took about a month to uncover an answer for my question. If I’d been on a client project, this wouldn’t have meant telling a PM/Producer/Scrum-Master/etc “No, we can’t do that because no one know what the heck
Magento_Ui/js/lib/knockout/extender/bound-nodes does”. With clearer docs, I’d have known right away.
Also, more importantly, with clearer docs and clearer intention, this bug would have been easily caught in the 2.0.x release and fixed by the 2.1.x release. Opaque system remain buggier because there’s fewer people who know what they’re for, and fewer people who can spot the bugs in question.
i.e. Good documentation doesn’t just help developers do their jobs, it helps everyone keep code quality up.