Configure reporting potential errors encountered during configuration call - #406
Merged
Conversation
… Also, allow calling configure multiple times (in case configuration failed the first time), which should be safe, since we're guarding around the session storage creation
3 tasks
Contributor
Author
Code Coverage
|
jhaven-stytch
requested review from
yzhang-stytch
and removed request for
mxbaylee
February 3, 2026 22:21
yzhang-stytch
approved these changes
Feb 4, 2026
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
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:
InitializationStatusclass that gives visibility into if it was completely successful, or if there were any errors. In the case of errors, we silently allow them and fallback to default values. This way, developers know if something went wrong.Notes:
Checklist: