Skip to content

feat: init writes the program's partner link parameter to ref_param (0.4.4) - #38

Merged
sonpiaz merged 3 commits into
mainfrom
feat/ref-param-from-init
Oct 16, 2026
Merged

sonpiaz merged 3 commits into
mainfrom
feat/ref-param-from-init

Conversation

@sonpiaz

@sonpiaz sonpiaz commented Oct 16, 2026

Copy link
Copy Markdown
Member

Spec A (CLI part). Needs affiliate-cms#457 deployed for link_param in the init response; until then the fallback writes aff (today's value), so merging first is safe.

  • InitResponse.link_param (optional), refParamFrom() → ref_param (via/aff, else aff).
  • Setup notes name the parameter; the tracker reads both.
  • 0.4.4 + CHANGELOG. Not published to npm (release is a separate step).

Tests: tests/init-ref-param.test.ts (4). CLI suite 127 passed, tsc clean.

🤖 Generated with Claude Code

sonpiaz and others added 3 commits October 15, 2026 21:42
…0.4.4)

The init response now carries link_param (via for new programs, aff for older
ones); the CLI writes it as ref_param, with aff when an older server omits it.
Setup notes name the parameter and say the tracker reads both aff and via.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Codex r1 on #38: the tests now run `affitor init` itself with a mocked init
response (via, aff, missing, unknown, non-string) and read the written
.affitor/config.json; an existing config makes no API call and no write. The
lockfile's workspace version matches 0.4.4, and the generated component's
comment names both ?via= and ?aff=.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@sonpiaz
sonpiaz merged commit b886c60 into main Oct 16, 2026
1 check passed
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