-
Notifications
You must be signed in to change notification settings - Fork 893
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
Set FirebaseError
name to be calling constructors name
#8553
Open
dlarocque
wants to merge
14
commits into
main
Choose a base branch
from
dl/firebaseerror-name
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
* Make memory lru gc the default * undo yarn.lock * Make memory lru gc the default * Fix tests
Our v11 release will require node 18+. Since fetch has been introduced in these node versions, we can remove our dependency on third party fetch implementations. This change removes our usage of fetch variants undici and node-fetch for our node target builds and our CI tools.
With the removal of fetch we no long need to create a node bundle for functions. Instead the sourcebase may become isomorphic, so long as we remove the older node sources. And that's what the PR does!
🦋 Changeset detectedLatest commit: ac00980 The changes in this PR will be included in the next version bump. This PR includes changesets to release 29 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1This report is too large (235,270 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
hsubox76
requested review from
erikeldridge,
jposuna,
avolkovi,
yoyomyo,
sam-gc,
yuchenshi,
lisajian and
Xiaoshouzi-gh
as code owners
October 17, 2024 21:07
hsubox76
requested review from
zwu52,
maneesht,
tonyjhuang and
aashishpatil-g
as code owners
October 17, 2024 21:07
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.
We currently set the error name to be
FirebaseError
and make it readonly. This means that whenever subclasses ofFirebaseError
callsuper()
, the name will be locked atFirebaseError
. This results in those errors from subclasses looking like:Subclasses should provide their own
name
property, so we should instead set the error name to be the name of the calling constructor. So if we dothrow new StorageError
,name
will beStorageError
. This makes errors look like this instead:This change will apply to all SDKs that have subclasses of
FirebaseError
(VertexAI, Storage, Functions, Auth).