Repository navigation
docs: sync the Guide with the Dart S3 auth findings - #23
Merged
Merged
Conversation
Replays through the same Dio, no lock around the single-flight check, resetAuth can't cancel a Future, Kotlin's auth decisions carried over, and RefreshResult's case names. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Regenerated from the vault after srctool/sinew-dart#59.
The Flutter Network part records:
Dio, not a separate auth-free one, and why.resetAuthcan't cancel aFuture; the epoch covers it.RefreshResult's case names.onSessionEnded.🤖 Generated with Claude Code