fix: use TAppState generic in ConnectAccountRedirectResult type #733
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed ConnectAccountRedirectResult<AppState> to ConnectAccountRedirectResult<TAppState> in handleRedirectCallback return type for consistency with RedirectLoginResult<TAppState>. This ensures both union types respect the generic parameter, maintaining type safety when consumers extend AppState with custom properties.
gyaneshgouraw-okta
approved these changes
Dec 22, 2025
yogeshchoudhary147
deleted the
fix/handle-redirect-callback-generic-type
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Fixed type inconsistency in
handleRedirectCallbackreturn type (line 312-313):Why
Both union types should use the same generic parameter for type safety and consistency with
RedirectLoginResult<TAppState>.Impact
AppState