bluerobotics / bluerobotics/cockpit
Action discovery (from BlueOS extensions) should have a versioning mechanism
Open
Actions
ux
- Dominant language
- TypeScript
- Stars
- 198
- Forks
- 63
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 57
Description
We should re-announce the action to the user whenever its versioning changes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how actions are discovered from BlueOS extensions and how they are announced to users. Define how an action version change is detected and re-announced; done means changed versions reliably trigger a new announcement without unnecessary repeats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100