Repository navigation
fix(storage): snapshotChanges should return a success snapshot - #2704
Merged
Merged
Conversation
jamesdaniels
changed the title
jamesdaniels
changed the title
Contributor
Author
|
It appears I'm going in circles here. I believe this is a JS SDK bug firebase/firebase-js-sdk#4158 I've put in enough work arounds to have things working decently IMO but developers still can't filter errors before they throw... |
jamesdaniels
changed the title
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.
Ugh this was still broken.
task.snapshotandtask.on('state_changed', ...)never return the "last" snapshot, have to use the promise form of task to get at it.Emits a filterable canceled or error snapshot prior to a throwThere appears to be a JS SDK bug blocking this 😢 in theory it should work in a future release