test(7736): the range case no longer puts "steps" before the first id
CI & Build / Plugin hooks (push) Successful in 13s
CI & Build / Python lint (push) Successful in 2s
CI & Build / TypeScript typecheck (push) Successful in 32s
CI & Build / Python tests (push) Successful in 1m50s
CI & Build / integration (push) Successful in 1m58s
CI & Build / Build & push image (push) Successful in 43s
CI & Build / Plugin hooks (push) Successful in 13s
CI & Build / Python lint (push) Successful in 2s
CI & Build / TypeScript typecheck (push) Successful in 32s
CI & Build / Python tests (push) Successful in 1m50s
CI & Build / integration (push) Successful in 1m58s
CI & Build / Build & push image (push) Successful in 43s
"step" is in the other-numbering word list ("step #3" is a position in
a plan), so "steps #5110" correctly stays plain. The case now tests the
range alone, and a second case pins the "step #3" reading.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -31,7 +31,10 @@ def _refs(notes=(), milestones=(), rules=()):
|
||||
|
||||
@pytest.mark.parametrize(("text", "expected"), [
|
||||
("see #123", _refs(notes={123})),
|
||||
("steps #5110–#5119 shipped", _refs(notes={5110, 5119})),
|
||||
("shipped #5110–#5119", _refs(notes={5110, 5119})),
|
||||
# "step" names a position in a plan ("step #3"), the same reading the
|
||||
# message parser uses, so a #N right after it stays plain.
|
||||
("step #3 of the plan", _refs()),
|
||||
("(#4286) and #4290.", _refs(notes={4286, 4290})),
|
||||
("#v2 is a tag", _refs()),
|
||||
("a colour #123abc", _refs()),
|
||||
|
||||
Reference in New Issue
Block a user