You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ce8be40
Browse filesBrowse the repository at this point in the historyBrowse files
fix(vscode): show an unconfigured Rstack lint config as not detected (#95)
Follow-up to #94 (#93). A bridged lint runtime whose root rstack.config.*
has no define.lint() reported `running` with a detail, which the status
bar hover rendered as a green check beside Rslint with the reason only
in the icon tooltip. The status bar's word for "this tool has no
configuration here" is `not-detected`, so the `unconfigured` verdict now
maps to `{ kind: 'not-detected', detail }` and the reason is shown as a
hover notice row.
- `StackState['not-detected']` gains an optional `detail`; only a
runtime-level "nothing configured" verdict sets it, detection never
does, so every other hover is unchanged.
- The status bar spells out the `not-detected` detail; one shared
`stackStateDetail` replaces the two identical switches in the shell
and the lint fold.
- `liveRslintStatus` / `reportLive` (renamed from `running*`) keep the
advisory-wins precedence; the worker stays up, no poll, no toast.
- Fold: an unconfigured-only folder stays `not-detected` with its
reason; a healthy native runtime beside it wins.
- AGENTS.md adaptation 7 and the lint-shim gotcha record the design,
including that the verdict lives with the runtime (an idle folder
reads `running: idle` until a document opens).
0 commit comments