Skip to content

Build FlexDoc 2.9 API Client execution, IntelliSense, and full history - #59

Open
bluejeans117 wants to merge 5 commits into
mainfrom
feat/api-client-2.9-execution-engine
Open

Build FlexDoc 2.9 API Client execution, IntelliSense, and full history#59
bluejeans117 wants to merge 5 commits into
mainfrom
feat/api-client-2.9-execution-engine

Conversation

@bluejeans117

@bluejeans117 bluejeans117 commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • extract API Client request execution into a reusable canonical executor shared by normal sends and collection execution
  • add collection-runner sequencing on top of the same request, auth, script, and variable engine
  • add dependency-free scripting IntelliSense for the flex.* runtime, including dot/Ctrl+Space completion, signatures, documentation, assertion-chain help, and known variables
  • promote request history from the compact recent list to a searchable and filterable full-page inspector with replay, deletion, response details, tests, logs, and preserved collection/folder provenance
  • persist response headers and bounded response bodies for new history entries while remaining compatible with existing workspace data
  • synchronize committed adapter renderer assets with the canonical 2.9 standalone build

Validation

  • client lint
  • complete client unit suite
  • canonical client/standalone build
  • adapter asset parity
  • full Chromium/Playwright renderer suite
  • exact-head repository CI and complete adapter matrix all passed

Compatibility

  • API Client workspace persistence remains backward-compatible; new history response fields are optional
  • older history entries remain readable even when they do not contain captured response payloads
  • history entries whose originating collection or folder was deleted retain explicit provenance labels and remain replayable through the current workspace fallback

Move request execution, scripting, auth resolution, interception, fetch timing, response tests, and mutation reporting into a reusable API Client execution utility. Keep the existing ApiClient UI behavior by delegating Send through the shared engine and expose the executor for the upcoming collection runner.
Add a sequential collection and folder runner built on the shared request executor. Carry collection and environment script mutations between saved requests, preserve inherited auth and history recording, centralize workspace mutation helpers, and expose runner APIs with focused coverage.
Replace plain script textareas with a dependency-free smart editor and phase-aware FlexDoc IntelliSense. Provide dot-triggered and Ctrl+Space completion, keyboard selection, signatures, documentation, assertion-chain help, and known variable names while keeping the catalogue covered against the scripting runtime.
Promote history from a compact sidebar list to a searchable full-page request inspector with replay, filters, response payloads, tests, logs, and deletion controls. Persist response headers and bounded response bodies for future history entries while remaining compatible with existing workspace data, with Chromium coverage for the filter and replay flow.
bluejeans117 added a commit that referenced this pull request Sep 5, 2026
Run the full client and browser validation against the history provenance and adapter asset synchronization fix before transplanting only product changes onto PR #59.
Preserve deleted collection and folder provenance in the full history view, update legacy browser coverage to use the full history workflow, and synchronize adapter renderer copies with the canonical 2.9 standalone build.
@bluejeans117 bluejeans117 changed the title Start FlexDoc 2.9 with shared API Client request execution Build FlexDoc 2.9 API Client execution, IntelliSense, and full history Sep 5, 2026
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