Skip to content

wxyc flowsheet start --specialty accepts a specialty-show slug - #12

Merged
jakebromberg merged 1 commit into
mainfrom
orchestrator/l6-wxyc-flowsheet-start-specialty-accepts-a-specia
Oct 21, 2026
Merged

jakebromberg merged 1 commit into
mainfrom
orchestrator/l6-wxyc-flowsheet-start-specialty-accepts-a-specia

Conversation

@jakebromberg

Copy link
Copy Markdown
Member

Closes #9

wxyc flowsheet start --specialty now takes a string. A numeric value is used as the specialty id (existing scripts keep working); anything else is resolved as a slug through GET /specialty-shows. An unknown or retired slug fails before the join with a one-line error listing the valid slugs. Any explicit --specialty value is honored (the old > 0 check is replaced by Flags().Changed). Help text now says the flag takes a slug. No new dependencies.

Tests: httptest-based tests cover slug, numeric, unknown-slug and retired-slug paths (cmd/flowsheet_test.go) and the new SpecialtyShows read (internal/api/reads_test.go).

Note: go build, go vet and go test -race were not run locally because the Go module proxy was unreachable from the sandbox; they run in CI.

--specialty now takes a program slug, resolved through GET /specialty-shows to the id sent as specialty_id on the join. A numeric value is still used as the id. An unknown or retired slug fails before the join with a one-line error listing the valid slugs.
@jakebromberg
jakebromberg merged commit 184faa1 into main Oct 21, 2026
1 check passed
@jakebromberg
jakebromberg deleted the orchestrator/l6-wxyc-flowsheet-start-specialty-accepts-a-specia branch October 21, 2026 09:49
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.

L6: wxyc flowsheet start --specialty accepts a specialty-show slug

1 participant