Possibility to reconfigure the json mapper?

[ghost]

Hi,

The following line in the ForceApi class is causing us some trouble:
jsonMapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);

force-rest-api/src/main/java/com/force/api/ForceApi.java

Line 50 in 8b64d0f

jsonMapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);

The problem we are having is that when an attribute currently has a value, but then that value was cleared, we receive that new value as "null" from our source system, but it never reaches Salesforce because this null value is ignored by the JSON serialization in ForceApi.

Was there a specific reason why this is the non-changeable default? Would it maybe be a good extension to make this configurable?

We'd be happy to create a pull request for this, were just wondering what the best way might be. Would it be too granular to introduce a boolean option in the configuration that says includeNonNull, with default value true? (In that case the jsonMapper couldn't be a static field anymore, would have to be an instance field that gets initialised in the constructor)

Thanks!

[jesperfj]

Can you provide a test that demonstrates the behavior you'd like? That'll be the fastest way for me to wrap my head around this. A pull request would be great, even if the implementation is speculative.

[jesperfj]

It would be lovely if you can take a look at my proposed changes in #51. This will allow you to use a custom object mapper of your choice. It was primarily designed to fix #45, but it might also help you. However, I really am not sure what will work for erasing field values. I haven't paid attention to that recently.

[ghost]

It seems like #51 would solve our issue, yes! Perfect.
In that case you can ignore our pull request :-)

Any plans when you are going to release 0.0.38?

[jesperfj]

0.0.38 has been released. Please check it out and let me know if things are working as expected.