Custom Element definition order matters

[joist-framework]

Custom Element definition order matters

[deebloo]

Approved and merged! Yeah let's close this issue and I'll open a new one to discuss other on code solutions for debugging. Thanks!

[deebloo]

Hey that's a good point! Agreed it should be added as a note in the di README. Ill look at add something soon. Happy to review a PR if you have a thought.

Sorry it tripped you up for so long!

[deebloo]

I'm not sure there is. Way to solve it in code, but I do wonder if there is a way make it easier to debug. For example at the moment it defaults to a global parent if not other parent is found in the DOM tree. That behavior could be changed. Something like inject(Ctx, { expectParent: true }); then we could throw and error if not parent is found and we can prompt the user to check definition order.

[Phoscur]

Yes, maybe that's what we actually want, a flag that allows us to explicitly request a parent override, which fails with a nice message/trace making it obvious when parent elements are not providing what they should.

Else it would be great to have a debug util or mode drawing dependency trees!

Provided a PR for a note in the readme, so that closes the issue for now?