Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

LSP reports `Unknown timer unit` for valid scalar timer units

Aperta
  • Qualcosa non va?
#643 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
devtools

Direzione di ricerca

Start by tracing the cook lsp entry point and how CookCLI invokes or pins cooklang-language-server; compare its timer-unit validation with the recipe parser that accepts the example. The report mentions related language-server issue #12, which may identify the relevant code path. Done when valid scalar timer units no longer produce an LSP diagnostic; verify against the reproduction and CLI behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: parser bug upstream

Problem

With CookCLI 0.36.0, the language server reports Unknown timer unit for valid scalar timers such as:

Boil for ~{25%minutes}.

The same recipe is accepted by cook recipe -f json, and cook doctor validate passes. In a collection of recipes, the LSP reported this for scalar minutes and seconds units, as well as the tested singular and abbreviated variants. This appears to be an LSP diagnostic mismatch rather than an invalid timer value.

Expected behavior

Timer units accepted by CookCLI's recipe parser should not be reported as unknown by the LSP.

Actual behavior

The LSP emits Unknown timer unit on the timer even though the CLI parses it.

Reproduction

  1. Create a .cook file containing the example above.
  2. Open it in an editor configured to run cook lsp.
  3. Observe the Unknown timer unit diagnostic.
  4. Run cook recipe -f json <file.cook>; the timer is parsed without that error.

Related: #214 covers cook doctor not reporting non-numeric timer values. That is a different case: this report uses a numeric value and concerns the LSP rejecting a unit.

I’d be interested in contributing a fix and would welcome guidance on the relevant code path.

Update: I retested with CookCLI 0.37.0 and still see the diagnostic. Neovim’s :LspInfo reports language-server version 0.2.4. The CookCLI v0.37.0 manifest pins cooklang-language-server 0.2.4, while the current CookCLI main manifest pins 0.3.0. I filed this against CookCLI because it’s the released cook lsp behavior I encountered. I also found the related cooklang-language-server issue #12. I’m happy to follow up in that repo if maintainers prefer.

Lingua principale
Rust
Stelle
1.4k
Fork
120
Merge medio
1g 22h
PR unite (30g)
128

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cooklang/cookcli

Tutte le issue di cooklang/cookcli

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.