Skip to content

fix: register graphql_bearer_auth_request + schema version + debounced auto-save#70

Merged
igorvieira merged 1 commit into
mainfrom
feature/graphql-bearer-fix-schema-debounce
May 4, 2026
Merged

fix: register graphql_bearer_auth_request + schema version + debounced auto-save#70
igorvieira merged 1 commit into
mainfrom
feature/graphql-bearer-fix-schema-debounce

Conversation

@igorvieira
Copy link
Copy Markdown
Collaborator

Summary

  • Register graphql_bearer_auth_request in main.rs invoke_handler — command existed in http/mod.rs:106 and was invoked from RequestContext.tsx:197, but missing from the handler list, breaking any GraphQL request with Bearer auth at runtime.
  • Initialize solo-schema-version=1 baseline in localStorage on first load, and exclude it from folder scans alongside solo-variables-* / solo-environments. Foundation for future storage migrations (Epic 2).
  • Debounce FileContext auto-save to 400ms via useRef+setTimeout, with flush on unmount and beforeunload. Removes per-keystroke localStorage writes; prerequisite for Epic 2.

Test plan

  • cargo check in src-tauri/ passes
  • bun run test — no new failures vs main (24 pre-existing styling-test failures unrelated to storage logic)
  • Manual: GraphQL request with Bearer token executes without "command not found"
  • Manual: rapid edits to payload write to localStorage at most every ~400ms
  • Manual: localStorage.getItem('solo-schema-version') === "1" after first run

…bounced auto-save

- Register graphql_bearer_auth_request in main.rs invoke_handler (was defined but unreachable from frontend)
- Initialize solo-schema-version=1 baseline on first load for future migrations
- Filter solo-schema-version out of folder scans alongside solo-variables-/solo-environments
- Debounce FileContext auto-save to 400ms with flush on unmount and beforeunload
@igorvieira igorvieira merged commit 3634481 into main May 4, 2026
1 check passed
@igorvieira igorvieira deleted the feature/graphql-bearer-fix-schema-debounce branch May 4, 2026 19:43
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