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 41f8592
Browse filesBrowse the repository at this point in the historyBrowse files
docs: describe concrete hints through jury.nvim and the public seams
Replace the "Jev enrichment" section with how jury.nvim fills the generic
hints, the install snippet for the pair, and the three things to know.
Document `set_hint_resolver`, `set_overload_picker`, `hint_family`, and the
templates in the public API. Mark the `typesafe` option as removed.
Copy file name to clipboardExpand all lines: README.md
+43-31Lines changed: 43 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -309,47 +309,47 @@ end,
309
309
|`sources`|`{ typescript=true, ts=true, vtsls=true, effect=true }`| Diagnostic sources this plugin handles. Exact match only. Merged with the defaults, so `{ deno = true }`*adds* Deno — pass `{ typescript = false }` to drop one. `effect` is `@effect/language-service`. |
310
310
|`format_ts_errors_fallback`|`true`| When no pattern matches, try [`format-ts-errors.nvim`](https://github.com/davidosomething/format-ts-errors.nvim) if installed. |
311
311
|`extra_patterns`|`nil`| List of `function(msg) -> {kind, ...}` parsers run after builtins. Let you add custom shapes. |
312
-
|`typesafe`|`{ enabled = false }`| Optional [Jev](https://docs.typesafe.ai) enrichment for overload errors. Off by default. See below. |
312
+
|`typesafe`|removed | Jev enrichment moved to [jury.nvim](https://github.com/rashedInt32/jury.nvim). The option is ignored with a warning. See below. |
313
313
314
314
If `float = true` and something else later calls `vim.diagnostic.config({ float = ... })`, Neovim replaces the whole `float` table — the formatter reinstalls itself on `LspAttach`, so the ordering doesn't matter.
315
315
316
-
## Jev enrichment (optional, off by default)
316
+
## Concrete hints with jury.nvim (optional)
317
317
318
-
A TS2769 "No overload matches this call." error carries one nested report per
319
-
candidate overload, and only one of them describes the call you meant to write.
320
-
The plugin picks with a hand-tuned heuristic: prefer an `Effect`/`Stream`/`Layer`
321
-
pair, then prefer the shallower report. That is a guess, and on a heavily
322
-
overloaded call like `Effect.gen` or a long `pipe` it can guess wrong.
318
+
Every `⚡ Hint:` line above is generic: `.pipe(Effect.provide(SomeLayer))`,
319
+
`.pipe(Effect.catchTags({...})) or Effect.orDie`. The parser knows the family
320
+
exactly, but not which layer you meant or which fix fits this function.
0 commit comments