Skip to content

refactor(provision)!: suffix the start scale pair _on_start - #14

Merged
mrcsin merged 1 commit into
masterfrom
on-start-rename
Oct 6, 2026
Merged

mrcsin merged 1 commit into
masterfrom
on-start-rename

Conversation

@mrcsin

@mrcsin mrcsin commented Oct 6, 2026

Copy link
Copy Markdown
Member

Problem

A semiplot_tags column holds either a live pen setting or a start value: what a pen opens with
in a new SemiPlot window, never changed by a chart already open. Start values carry the
_on_start suffix, but only enabled_on_start did; the start scale pair was
scale_min/scale_max. Semiteq/SemiPlot#72 adds a third start value, so the naming is made
uniform first.

Change

  • scale_min/scale_max become scale_min_on_start/scale_max_on_start in the CREATE TABLE, the semiplot_tags_scale_paired constraint, plotEditableTagColumns (the semiplot
    column grant and the write probe) and the four tests that spell the column set out.
  • No installation exists yet, so the rename edits the CREATE TABLE alone: no ALTER,
    schema_version stays 1. docs/architecture says the version rule starts with the first
    installation.
  • Breaking for any client naming the old columns. The SemiPlot side follows in its own pull
    request right after v0.5.0.

Verification

  • go test -count=1 ./..., go vet ./..., golangci-lint run: pass, 0 issues.
  • git grep -nw "scale_min\|scale_max" -- ':!docs/plans' prints nothing.
  • site twice on PostgreSQL 17 and bench on 14 ran against throwaway containers during
    review; the CI linux job on this pull request is the gate.

A semiplot_tags column holds either a live pen setting, which a running
SemiPlot chart picks up at the next catalogue read, or a start value:
what a pen opens with in a new window, never changed by a chart already
open. Start values carry the _on_start suffix. Only enabled_on_start did;
the start scale pair was scale_min/scale_max.

Rename the pair to scale_min_on_start/scale_max_on_start in the CREATE
TABLE, the semiplot_tags_scale_paired constraint, the semiplot column
grant and the tests that spell the column set out. No installation runs a
database provisioned by an earlier release, so the rename edits the
CREATE TABLE alone, issues no ALTER and keeps schema_version at 1. A
database provisioned by v0.4.0 is recreated, not provisioned again.
@mrcsin
mrcsin marked this pull request as ready for review October 6, 2026 14:54
@mrcsin
mrcsin merged commit 34163ec into master Oct 6, 2026
2 checks passed
@mrcsin
mrcsin deleted the on-start-rename branch October 6, 2026 14:58
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