feat(conventions+gate): api-client collection paths carry a TRAILING SLASH (build14 endgame wall)#155
Merged
Merged
Conversation
… (build14 endgame wall)
build14 reached best=1 error (closest to green ever, all 4 prior walls cleared) then
oscillated ~40 turns on `PathsWithMethod<paths,"post">` for POST /api/v1/supplier — the
generated key is /api/v1/supplier/ (WITH trailing slash): Elysia mounts the group at
/api/v1/<resource> and the create/list handler at '/', so the collection root key carries
the slash. The model discovered it itself at turn 157 but ran out of runway.
data-fetching guide now teaches: collection root = /api/v1/<resource>/ (list GET + create
POST, TRAILING SLASH); by-id = /api/v1/<resource>/{id} (no trailing slash). Examples +
regression test updated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #154. build14 reached best=1 error (all 4 prior walls cleared) then oscillated ~40 turns on PathsWithMethod POST /api/v1/supplier — the generated key is /api/v1/supplier/ (trailing slash: Elysia .group + .post('/')). Verified general (scaffold uses /api/v1/notifications/, schema has /api/v1/{capabilities,notifications,supplier}/). data-fetching guide + the PathsWithMethod per-error steer now both teach: collection root = /api/v1// (list+create), by-id = /api/v1//{id}. Panel PASS; full suite green (2832).