-
Notifications
You must be signed in to change notification settings - Fork 923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emulator Idempotency: Auth #8750
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
177cde1
connectAuthEmulator idempotency
DellaBitta e0ba6df
Added tests.
DellaBitta ce6341a
Return if already attached.
DellaBitta bc79c7c
Added changset and test comment updates.
DellaBitta d9fa204
Use deepEqual instead comparing JSON.
DellaBitta 71ee5cb
Added more descriptive state checking for asserts
DellaBitta c829d99
Update lemon-candles-vanish.md
DellaBitta File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
--- | ||
'@firebase/auth': patch | ||
'firebase': patch | ||
--- | ||
|
||
Fixed: invoking `connectAuthEmulator` multiple times with the same parameters will no longer cause | ||
an error. Fixes [GitHub Issue #6824](https://github.com/firebase/firebase-js-sdk/issues/6824). | ||
|
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this technically works but it doesn't make the logic clear. There's two reasons to throw here, one is if they're calling this for the first time too late (after a network call has been made, that's the purpose of
authInternal._canInitEmulator
), and the second reason is if they're calling it for a second time with different args. This makes it look like we're only targeting the second case. It will actually work on the first case, of course, because the local varsemulator
andemulatorConfig
will have some properties, and won't match{}
, but I guess the fact it's nested inside adeepEqual
doesn't make it clear that's a case we're trying to block on.I know it's more verbose, but instead of the
|| {}
maybe a separate_assert
before this one that just tests for the existence ofauthInternal.config.emulator
andauthInternal.emulatorConfig
would make it clearer that we're covering 2 different cases?