-
Notifications
You must be signed in to change notification settings - Fork 362
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
FirestoreDbBuilder.ConverterRegistry ignored when using Firestore Emulator #6313
Comments
I'll have a look when I'm back at work tomorrow. It's almost certainly just a bug. |
(I suspect it will be a bug that's easily fixed, and which we can then just roll out a patch release for. But we'll see...) |
Thanks! Good to know this could be fixed soon. |
Changes in this release: - [Commit 62182ca](googleapis@62182ca): fix: Propagate properties in FirestoreDbBuilder when using the emulator. Fixes [issue 6313](googleapis#6313) (No API surface change, as expected in a patch release.)
Hi @jrojasledesma, the fix is now released in version 2.3.1. I'm pretty confident in the fix, but please shout if you have any problems :) |
Hi, I just tried the new version and confirmed that my issue is now fixed. Thank you @jskeet and @amanda-tarafa! |
Hi. I'm having problems trying to use custom type converters via the Converter Registry in FirestoreDbBuilder when targeting the Firestore Emulator.
Looking a the source code I noticed that FirestoreDbBuilder ignores the value of its ConverterRegistry property when creating an instance of FirestoreDb. The problem seems to be in lines 186-192 of FirestoreDbBuilder.cs, inside the function
MaybeUseEmulator
:Note that in the new FirestoreDbBuilder returned by this method, ConverterRegistry is not asigned. Thus, the original value is ignored when the FirestoreDb instance is created in the recursive call to
Build
in line 89 of FirestoreDbBuilder.cs.Is there any good reason to ignore the value, or is this simply a bug?
The text was updated successfully, but these errors were encountered: