aviatesk / aviatesk/jetls-vscode
Enhancement request: Better status markers for file status in VS Code
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 17h 51m
- Merged PRs (30d)
- 14
Description
I find myself watching the lower-left corner a lot to see the LS working.
The problem is that it can take several seconds after saving sometimes for the spinner to start, and I'm often not sure whether it missed an update. Sometimes, the opposite happens and the analysis completes so quickly (or I was distracted) that I miss the little loading status. However, I can't tell that it's already done and found no issues.
Not 100% sure what the best solution is, but it seems like a permanent JETLS "status" entry in the taskbar would be useful to report the current file status (e.g. excluded from analysis, up-to-date, awaiting re-analysis, etc.)
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the VS Code extension code that drives the lower-left JETLS spinner, then determine how a permanent status entry could represent excluded, current, awaiting re-analysis, and completed states. Done should make file-analysis status consistently visible and distinguish completion with no issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100