-
Notifications
You must be signed in to change notification settings - Fork 992
Storage Emulator "Fast-Follow" Bug Fixes #3403
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
Conversation
2bfecd2
to
ec366f8
Compare
} | ||
|
||
private deleteFieldsSetAsNull() { | ||
const deletableFields: (keyof this)[] = [ |
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 just learned a new trick!
|
||
if (this.customMetadata) { | ||
Object.keys(this.customMetadata).map((key: string) => { | ||
if (!this.customMetadata) return; |
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.
This if
seems to conflict with the outer if(this.customMetadata)
...
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.
it doesn't conflict cause it's saying "if I have custom metadata do this" then "if I dont have custom metadata dont do this" but it is weird cause it's like a double check. I had to add this cause typescript was getting confused and ignoring my explicit check of this.customMetadata
in the outer if
thinking it could still be undefined
in the inner one so I had to check again.
Tho it occurs to me that if I use a for
look it'll probably fix this so I'll probably just do that.
See Changelog.md for details.