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

未关闭
#413 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 分钟
30 天内合并 PR
362

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AlphaWaveSystems/flutter-probe 的其他 Issue

查看 AlphaWaveSystems/flutter-probe 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。