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

Ouverte
#413 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Calme
Stack technique
flutter, go
Domaine
testing-qa, tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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).
Langage dominant
Go
Étoiles
6
Forks
3
Merge moyen
6 h 28 min
PR mergées (30 j)
362

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de AlphaWaveSystems/flutter-probe

Toutes les issues de AlphaWaveSystems/flutter-probe

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.