# Description

Previously, the `Asset` classes assumed that the root prim existed at
the spawn prim location. This means that when the robot is spawned at
`/World/Robot`, the articulation root prim is also at `/World/Root`.
However, this is not safe operation as many assets will have the root
defined under the spawn location.

The MR safely checks if there are prims under the spawn location that
have the API defined for them. If they do, then it uses that prim path
for initializing the views.

## Type of change

- New feature (non-breaking change which adds functionality)

## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./orbit.sh --format`
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] I have updated the changelog and the corresponding version in the
extension's `config/extension.toml` file
- [x] I have added my name to the `CONTRIBUTORS.md` or my name already
exists there