fix(boringstack): steer PathsWithMethod errors to register the route (not fight UI types)#149
Merged
Merged
Conversation
…(not fight UI types)
build6 residual (after testing+WS-B fixes): the model wrote UI calling
apiClient.<M>('/api/v1/supplier') before the API route was in the OpenAPI spec →
'not assignable to parameter of type PathsWithMethod<paths,"post">' → it fought the
UI types + coupled test-sibling for 20+ turns instead of touching the route. Enrich
that error class in signatureToError: a PathsWithMethod rejection means the path
isn't in the spec — register/mount the route, let the gate regenerate the client,
then the type exists; fix the route, not the call site. Same seam + shape as the
parse-steer. Unit test for the enrichment + a plain type error untouched.
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.
build6 residual: the model wrote UI calling
apiClient.<M>('/api/v1/x')before the API route was in the OpenAPI spec →not assignable to PathsWithMethod<paths,…>→ it fought the UI types + coupled test-sibling for 20+ turns. Enriches that error class insignatureToError: a PathsWithMethod rejection means the route isn't in the spec — register/mount it, let the gate regenerate the client, then the type exists. Same seam as the parse-steer. Unit-tested.