**Parse IF<n> token for infield-fly commands** #47

Closed
opened 2026-04-09 14:31:20 +02:00 by umpire274 · 0 comments
umpire274 commented 2026-04-09 14:31:20 +02:00 (Migrated from github.com)

Parse IF token for infield-fly commands

The infield-fly branch only matches strip_prefix("IFF"), so documented commands like 7 IF4 / 7 if4 do not parse and fall through to Unknown. This makes the advertised infield-fly syntax unusable in live scoring unless users enter the non-documented IFF<n> form. Please accept the IF prefix here so parser behavior matches the command grammar.

Useful? React with 👍 / 👎.

Originally posted by @chatgpt-codex-connector[bot] in https://github.com/umpire274/bs_scoring/pull/46#discussion_r3057788082

**Parse IF<n> token for infield-fly commands** The infield-fly branch only matches `strip_prefix("IFF")`, so documented commands like `7 IF4` / `7 if4` do not parse and fall through to `Unknown`. This makes the advertised infield-fly syntax unusable in live scoring unless users enter the non-documented `IFF<n>` form. Please accept the `IF` prefix here so parser behavior matches the command grammar. Useful? React with 👍 / 👎. _Originally posted by @chatgpt-codex-connector[bot] in https://github.com/umpire274/bs_scoring/pull/46#discussion_r3057788082_
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
umpire274/bs_scoring#47
No description provided.