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

オープン
#413 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
flutter, go

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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).
主要言語
Go
スター
6
フォーク
3
平均マージ
6時間 28分
マージ済み PR(30日)
362

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

AlphaWaveSystems/flutter-probe のほかの issue

AlphaWaveSystems/flutter-probe の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。