Skip to content

feat: say when a test key could not confirm a code - #95

Merged
Adeniyikayodee merged 3 commits into
mainfrom
feat/test-key-note
Oct 12, 2026
Merged

Adeniyikayodee merged 3 commits into
mainfrom
feat/test-key-note

Conversation

@Adeniyikayodee

@Adeniyikayodee Adeniyikayodee commented Oct 12, 2026 •

Copy link
Copy Markdown
Owner

With a test key NIPOST answers not_found for every code we have tried, including ones a live key confirmed (noted in docs/api-differences.md since 6 October). --confirm then wrote false for every row, and the resolver told the user their code was not assigned.

  • The Python clients expose test_key.
  • ng-postcode --confirm prints one line when it is given a test key.
  • The resolver adds the caveat to its evidence. The decision itself is unchanged.

That test keys see no buildings is our reading of two keys, and NIPOST has not confirmed it, so the wording says "may".

@Adeniyikayodee
Adeniyikayodee merged commit dff03d2 into main Oct 12, 2026
18 checks 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