Closed BrianHung closed 11 months ago
Hey @BrianHung - not sure if this PR is ready for review yet or not, and I see you have another open PR as well. Thanks for putting these together!
If you are still working on them, disregard this comment. I just wanted to let you know I saw it and I'm stoked to get 'em merged. I am about to be away from my computer until next week, so I won't have time to look things over. I'll tag @jamonholmgren if he's got time, but I don't know his schedule so I won't speak for him.
Would you mind doing a couple things:
Thanks again! If Jamon doesn't get to this stuff before I'm back, I'll try and take a look next week. Feel free to ping me about it by the end of next week if there's no movement here.
Thanks for the updated description, @BrianHung! I played around a bit with the code here and it makes sense to me. With CI passing, tests looking good, i'm going to merge it.
I've opened up https://github.com/mobxjs/mobx-state-tree/pull/2049, which I'll work on sourcing someone for in terms of tests and docs. But I think the change is pretty safe as-is, and you'll be able to start using it directly from the next minor release (unsure when that'll actually be).
https://github.com/mobxjs/mobx-state-tree/discussions/2011
This PR gives complex types (array, map, and object) debug names. The human-readable names appear in MobX error messages and in the trace utility. MST already has a method called
describe
on each complex type that we can reuse for the MobX names.