Skip to content

test(client): cover autocomplete without a segment - #8

Merged
MobileMage merged 1 commit into
gatepost-dev:mainfrom
lui01212:codex/autocomplete-missing-segment
Oct 4, 2026
Merged

MobileMage merged 1 commit into
gatepost-dev:mainfrom
lui01212:codex/autocomplete-missing-segment

Conversation

@lui01212

@lui01212 lui01212 commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Add the missing-segment cases requested in #5, with both empty and non-empty suggestions.
Both responses raise unexpected_response on the existing implementation. This change adds tests
only, so it needs no change file.

composer check, unit tests on PHP 8.1 and 8.5, contract tests against the mock server on both
versions, sign-off and squash-message checks pass on the fork.

CI: https://github.com/lui01212/php/actions/runs/37173552823

Closes #5

Codex helped write the two regression cases and review the diff.

Signed-off-by: Lui Lui 40736418+lui01212@users.noreply.github.com

Add empty and non-empty suggestions without a segment to the unreadable
response cases (T-4). Both must raise unexpected_response, as issue gatepost-dev#5 asks.

Signed-off-by: Lui Lui <40736418+lui01212@users.noreply.github.com>
@MobileMage
MobileMage merged commit 1773243 into gatepost-dev:main Oct 4, 2026
9 checks passed
@MobileMage

Copy link
Copy Markdown
Contributor

Merged as 1773243. Both cases sit where a reader looks for them, in the existing provider, and the second one (a missing segment with a suggestion present) is the case that a quick fix would miss. That is three merged changes across three repos now. The open good first issue items in spec are free if you want another.

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.

Test that autocomplete with no segment gives unexpected_response

2 participants