Skip to content

feat: send an undocumented runtime route from the API Client - #191

Merged
bluejeans117 merged 5 commits into
mainfrom
feat/execute-runtime-only-route
Sep 22, 2026
Merged

bluejeans117 merged 5 commits into
mainfrom
feat/execute-runtime-only-route

Conversation

@bluejeans117

@bluejeans117 bluejeans117 commented Sep 22, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • LOOP-03: the registered route that OpenAPI does not document can be opened in the API Client with its method and path filled in.
  • When host execution is available, that request prefers the API host. Otherwise it stays a browser request.
  • The page still does not invent a schema or a handler.

Test plan

  • Handoff includes POST https://api.example.test/internal/reindex and preferHostExecution: true when the host is available
  • Handoff omits host execution and uses the path alone when the host is unavailable
  • Documented operations still render after a runtime-only route
  • Client typecheck passes and adapter assets match the standalone build
  • CI on this pull request

Opening the finding showed the registered method and path and then
stopped. The same page now hands that request to the API Client. When
the documentation server can execute from the API host, the request
prefers that transport.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
Discovered paths already include their mount prefix. Prepending a server
URL that also has a base path sent the request to the wrong place, and
the configured server hid the origin that registered the route. The URL
is now that origin plus the runtime path.

The request asks to prefer the API host only when the server has not
opted out. A server preferHostExecution of false still selects the
browser, the same as a documented operation.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
The handoff records the registering origin as the current server, and
the runtime path already includes its mount prefix. Switching to an
OpenAPI server whose URL also has that prefix appended the path twice.
The switch now keeps a suffix that already starts with the next
server's base path.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
Acknowledgement was removing a route from the drift counts so the
status could go green. The route stays registered. The finding remains,
with disposition acknowledged and info severity, and it does not fail
validation. The Node examples acknowledge GET /internal/health and leave
POST /internal/reindex unacknowledged so the check still fails.

A runtime-only request uses the snapshot origin, or a same-origin path
when that origin is absent. It does not borrow an OpenAPI server. The
generic server switcher is unchanged.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
The hash listener resolved only spec operations, so opening an undocumented route cleared the page before the contract gap could render.

Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
@bluejeans117
bluejeans117 merged commit 77bc061 into main Sep 22, 2026
21 checks passed
@bluejeans117
bluejeans117 deleted the feat/execute-runtime-only-route branch September 22, 2026 15:41
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