Peter Weinberg

> I'm not sure if this works - but if it does, you would effectively be updating the computed prop whenever state (and all of its children) changes - based...

@jmyrland @ROTGP I've dug into the code a bit more and found out that unless you use state resolvers, the input to the computed property is the parent store's state....

Thank you @jmyrland and @ctrlplusb! This is awesome!

Is type info on hover pushing it? 😄

@dschach Absolutely no rush. As you know from working with me on this repo in the past I have a lot going on as well and am not checking in...

Hey, sorry, I've been totally swamped lately. Will take a look in the next couple days.

@dschach The PR looks mostly good at this point, thanks for addressing the review comments. Any idea what's up with the yarn.lock file, though? I only see one dependency change...

Also, I'm assuming you've tested this and everything looks good on your end? If so, since there's no change to core documentation generation code here, I won't feel the need...

@dschach Thanks - I think my preference at this point would be to remove husky (and the changes to the lock file) until we need it for something. When we...

@dschach reverted lockfile changes and removed the `prepare` script from `package.json`