DiamondLightSource / DiamondLightSource/blueapi
Remove async api if it is not used by other clients downstream
- Dominant language
- Python
- Stars
- 13
- Forks
- 13
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 25
Description
I don't know if we are using it somewhere, but we should not break it without investigating where this is used.
I suggest we create a issue to track removing this from blueapi, But let this PR in so that we can have the latest changes without breaking anything.
_Originally posted by @ZohebShaikh in https://github.com/DiamondLightSource/blueapi/issues/1656#issuecomment-5582978063_
Contributor guide
Research direction
Start with the async API referenced in this issue and review issue #1656 for context. Investigate whether downstream clients use it before deciding the removal scope; the work is complete when usage is documented and a follow-up removal plan or issue is established without breaking dependent clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100