You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use that for a job system and I write the serialized payload to the job table. If something goes wrong (which does not happen very often) I do not have to serialize it again.
I want to be independent from the serialization in algolia. For example I have migrated to System.Text.Json a few years ago, which Algolia was still using Newtonsoft. I also have dozens of custom converters that I need to serialize it properly.
As an alternative I would probably deserialize it into a JsonDocument (from System.Text.Json) and then the client would serialize it again).
In my current project, we would also benefit from being able to add the objects directly serialized by us (because we also use custom converters) to Algolia.
This way we could also take advantage even more of the schemaless way Algolia is storing the data.
What is about my JRaw? It is relatively easy to implement with a custom converter and it would be great to accept serialized objects: https://learn.microsoft.com/en-us/dotnet/api/system.text.json.utf8jsonwriter.writerawvalue?view=net-6.0
An alternative could be to pass a JsonSerializerOptions.
Originally posted by @SebastianStehle in #852 (comment)
The text was updated successfully, but these errors were encountered: