Remove OpenXR from all public facing interfaces and make it an implementation detail
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 385
- Forks
- 88
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 82
Description
OpenXR should not be a part of the public tracker interface, and it is an implementation detail
This is part of future-proofing the API for replay-based backend for teleop instead of live OpenXR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the public tracker interface and all OpenXR references in the Python project. Trace which OpenXR types or names cross that interface, then verify that the public API no longer exposes them while OpenXR remains usable internally for live teleoperation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100