Skip to content

Add Optional Refresh Token Handling to NetworkManager #129

@ahmtydn

Description

@ahmtydn

Description

This issue proposes the introduction of optional refresh token handling in the NetworkManager class.


Problem

Currently, all requests made through NetworkManager implicitly rely on refresh token handling, which can lead to unnecessary overhead for public or unauthenticated endpoints.


Proposed Solution

Add a new optional parameter disableRefreshToken to the send and sendRequest methods. This will allow developers to explicitly disable token refresh logic for individual requests.


Acceptance Criteria

  • A disableRefreshToken boolean parameter is added to the send and sendRequest methods.
  • If disableRefreshToken is true, token refresh logic is skipped for that request.
  • If not provided, the behavior remains backward compatible (defaults to current behavior).
  • Documentation is updated with usage examples.

Benefits

  • Greater control over authentication flows.
  • Improved performance by avoiding unnecessary token refresh operations for specific requests.
  • Cleaner codebase with per-request flexibility.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions