Antoine Hémery

After digging more into the subject I found a balanced strategy we could consider to implement `System.Text.Json` (the new standard library) instead of `Newtonsoft.JSON` (the dependency we have for the...

https://github.com/algolia/algoliasearch-client-csharp/blob/d62f15ebd5964b54fec3d9e06380bf379c7ad86b/src/Algolia.Search/Models/Search/Query.cs#L372-L376 It should be OK, but I'd rather add a UT for it.

Hello, Thanks a lot for submitting your PR, we appreciate the time you passed working on it. However, I am afraid we won't be able to merge it -as it-...

Hi! Thanks for the reporting the issue. I'll have a look at it in the coming days.

Hi, The library is meant to be used with `POCO` or `JObject` to ensure our users they are sending correct data to the API. That's why the `saveObjects` method is...

It was made on purpose to help our users to migrate from v5 to v6. However, we could consider making this additional check optional for `dynamic` and `dictionary` as well...

Hello, Can you elaborate on your use case? Would you also have some numbers/benchmarks to share regarding the GC/memory pressure?

Hi @vicero Thanks for the feedback. This is definitely something I wanted to address in the next version of the library since .NET Core 3 will be shipped with a...

What kind of performance issues are you facing? Memory/speed or both? Are you facing this issue at Indexing time or at Search time?

Alright. I'll work on the injection of the serializer in the coming days. In the meantime, another work-around could be to reduce the size of the response with the [responseFields](https://www.algolia.com/doc/api-reference/api-parameters/responseFields/)...