Making ObjectMapper injectable

[Ant-hem]

What do you think of letting our users inject their own ObjectMapper? It could be injected like the HTTP Client. I am opening this issue because it's not the first time I got the request.

WDYT? @BenoitPerrot @aseure

[aseure]

Disclaimer: I'm not sure of all the implications it would have.

My initial thought is that it could lead to users reporting issues with failed serialization/deserialization of legit Algolia requests and responses (correct me if I'm wrong here @BenoitPerrot).

Side question: are there things which cannot be done because the ObjectMapper is not injectable?

[Ant-hem]

Also found a stackoverflow question about it.

Thing is, we were allowing it in the v2 of the client.

[Benji1109]

Hi, Is there any update on this?

[tomaytotomato]

This is a really necessary feature

For example where Algolia fields are snake case e.g. number_of_employees, it would have been great just to define a

@JsonProperty("number_of_employees")
Integer employees;

This keeps Algolia schema design from polluting Java coding standards, as now I am forced to have a property in my class called.

Integer number_of_employees;

Also because ObjectMapper is not injectable or SearchConfig extendable I cannot override this.