Strict assertions: make exact text matching easy and warn when a check can pass vacuously

Aperta
#413 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
flutter, go

Direzione di ricerca

Read the parser, lint implementation, grammar documentation, conformance tests, MCP tool descriptions, mcp.md, VS Code extension surfaces, dictionary, see documentation, and CHANGELOG. First confirm the exact-text form with the maintainer in the PR description, then trace how see and wait until ... appears text is parsed and linted. Done means the additive exact-text guidance and suppressible warning meet the acceptance criteria, with parser, conformance, and positive and negative lint tests updated.

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

Descrizione

area/cli enhancement

Problem

Text selectors match substrings. A zero-state check such as see "0 ml" also passes on "250 ml"-style text that contains it, or on any widget whose text includes the string, so the check can pass without testing what the author meant. Users have hit this in real suites. The workaround today is an anchored regex (see "0 ml" matching "^0 ml$"), which is hard to discover.

Constraints

  • Additive only: existing grammar, probe.yaml and report JSON keep working. Exact-by-default would change the meaning of existing tests, so it is not an option for 0.x.
  • Any parser change updates the complete EBNF in the grammar docs and the conformance test (hard rule).
  • Every new keyword or flag also updates the MCP tool descriptions, mcp.md, the VS Code extension surfaces and the dictionary.

Acceptance criteria

  • A documented, discoverable way to assert exact text (either a new additive form such as see exact "X", or a documented matching "^...$" idiom with an example on the see page). Maintainer to confirm the form in the PR description before implementing.
  • A probe lint warning when a see or wait until ... appears text looks like a zero-state or short numeric string (for example matches ^[0-9]+( [a-z]+)?$), pointing to the exact form. Warning only, never an error, with a way to silence it.
  • The see and dictionary docs say that text selectors match substrings and that exact is preferred for zero-state and count checks.
  • Tests: parser and conformance, lint warning positive and negative cases.
  • CHANGELOG entry (additive).
Lingua principale
Go
Stelle
6
Fork
3
Merge medio
6h 28m
PR unite (30g)
362

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 AlphaWaveSystems/flutter-probe

Tutte le issue di AlphaWaveSystems/flutter-probe

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.