Skip to content

Move every auth-ui operation onto the globally configured client #39

Description

@ExtraToast

What to build

Every operation in this application routes through the globally configured client rather than passing configuration per call.

This matters beyond tidiness: generated query options build their cache key from the options object, so passing base URL or headers per call would key the cache on request configuration including auth headers.

Acceptance criteria

  • No call site passes base URL, credentials or headers
  • Authentication and CSRF still work on every operation, proven end to end
  • Cache keys derive from the operation, not from request configuration

Blocked by

  • Tracer bullet: fetch the current user end-to-end through the new pipeline

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: authAuthentication, authorization, sessions, or identity.component: uiUser interface component or frontend application.priority: P1High; important and should be handled in the current iteration.type: refactorCode structure change without intended behavior change.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions