Matthew Pomes

Looking into this, it actually seems fairly trivial to add support for testing which route handled a given request. The actual mechanics are somewhat complicated, but the `LocalResponse` type actually...

> > How can all the data not be available for reading? > > `Data` can only be read from once, since it is a live connection to the client....

I'm not sure if animations is the right place to put this, since it might belong in core or ecs (given that is could be used more generally, even if...

After some analysis, I think it might be possible to remove `EntityPath` altogether. My initial assumption was that the `EntityPath` matched the gltf format, but after looking into the format,...

> > it's actually possible for AnimationClip to store the actual Entity id, rather than the path > > That's actually not possible because an `AnimationClip` can be applied to...

After careful reflection, I've chosen to revert back to my original goal with this PR, and open a new PR when and if I have a more complete solution. For...

> CI seems to be lost with your force pushes. Could you push a new commit to trigger it? And put the PR out of draft if you're happy enough...

I think I've reached an API I'm pretty happy with. Since the type tracking is done internally, this could be extended to support listing the routes attempted in order, but...

@cataggar #2167 is specifically intended to address this issue. It also implements the route tracing noted above.

I think taking option 1, with a note suggesting data-structure authors should also re-export the `unique_domain!` macro is the simplest option. Authors who wish to take the second option can...