Skip to content

fix: correct sqb mv plurals and plain-language plan bounds - #961

Merged
kvlonge merged 1 commit into
mainfrom
fix/mv-plurals-and-bounds-wording
Oct 6, 2026
Merged

kvlonge merged 1 commit into
mainfrom
fix/mv-plurals-and-bounds-wording

Conversation

@kvlonge

@kvlonge kvlonge commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Why

sqb mv and sqb rename printed "1 files", and sqb plan showed bounds runtime-owned (model-backed cursor input) in bold, even for seed and source cursor inputs.

Changes

  • Rename/mv progress and status lines use the shared count helper (1 file, 2 files).
  • The plan bounds line names the cursor inputs and their kind in plain words, e.g. computed at run time, once seed payments is up to date, styled like the other properties. The deferred microbatch batches line uses the same wording.
  • Removed the rule that bolded any value containing "runtime" or "deferred".
  • JSON output unchanged.

Verification

  • New unit and integration tests for singular/plural lines and the bounds line with model, seed, source and several inputs; they fail without the fix.
  • Focused pytest (98 passed), ruff, fensu check and make check-ci.

…ds wording in sqb plan

sqb mv and sqb rename printed "Planned edits to 1 files.", "Writing 1
files..." and "Wrote 1 files."; they now use the shared count helper.

sqb plan described a model whose cursor range is found during the run as
"bounds  runtime-owned (model-backed cursor input)", even when that input
was a seed or a source, and showed it in bold. It now names the input and
its kind, for example "bounds  computed at run time, once seed payments
is up to date", with the same styling as the other property values. The
deferred microbatch count line uses the same wording instead of "after
upstream models complete". Plan JSON is unchanged.
@kvlonge
kvlonge enabled auto-merge (squash) October 6, 2026 06:40
@kvlonge
kvlonge merged commit ea7c27b into main Oct 6, 2026
30 checks passed
@kvlonge
kvlonge deleted the fix/mv-plurals-and-bounds-wording branch October 6, 2026 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant