[lang] stricter annotation building
Open
discussion
enhancement
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 167
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] check for unknown annotations
- currently does not blow up if annotation is not known
- [ ] check for annotations used multiple times
- currently that's allowed (last one wins)
Contributor guide
Research direction
No files, tests, or entry points are named in the issue. Start by locating the annotation-building logic and its existing tests, then trace how unknown and repeated annotations are handled. Done means unknown annotations fail and duplicate annotations are rejected rather than allowing the last one to win.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100