-
Notifications
You must be signed in to change notification settings - Fork 494
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
CosmosSerializer not honored in LINQ queries #1936
Comments
@khdang Do you have any comment on this one? |
This is a duplicate of #1782 |
Please try the 3.17.0 nuget. |
Sorry for closing this. I got the issues number mixed up. This could be address with a new linq serialization option. |
Any news on this? Still having the same problem as described by question author. |
@j82w Any update? |
Hi all, we've merged what we hope will be a solution to this issue by allowing the custom serializer to be used for LINQ translations. This also unblocks having System.Text.Json attributes applied in LINQ queries. We plan to release this as part of the next preview package, but I also wanted to take this time to confirm these changes meet your needs before finalizing them as part of our public API. If you try the changes out, please follow up in the thread if this update addresses your concerns. If it doesn't, please let us know why. To use your own custom serializer for LINQ translations you must implement |
It seems like LINQ queries use CosmosSerializationOptions for serialization of fields, but it does not supports ENUM to String conversion. And If i use CosmosSerilaizer then it is not honored by LINQ queries, is there a workaround without decorating field with [JsonConverter(typeof(StringEnumconverter)] and make LINQ queries work for ENUM fields ?
The text was updated successfully, but these errors were encountered: