Delegate parsing and writing of value types to Gson

[papegaaij]

This allows registering custom TypeAdapters to customize (un)marshalling of these value types. This fixes #2053.

I've decided not to pass methods like getFloatValue to the Gson instance. The gson.fromJson calls do impose some overhead and they all end up in the corresponding JsonElement.getAsXXX methods. I did make it easier to subclass JsonParseNode to create your own subclass if needed. That would allow a user to override one of the primitive parsing methods.

[baywet]

Thanks for the contribution!

In addition to the comments left inline, I think we should also have the "primitive" types use the adapter model for consistency with dotnet, and for consistency of behaviour.

https://github.com/microsoft/kiota-dotnet/blob/ae9a82ff2d1445ad2f1ef26a9d9e918a402b8a26/src/serialization/json/KiotaJsonSerializationContext.cs#L11

[papegaaij]

Now that JsonParseNode delegates parsing of all value types to Gson, the implementation is no longer symmetric. Maybe, the JsonSerializationWriter should also delegate writing for all value types to Gson? So rathter than calling writer.value(bool), it will be gson.getAdapter(Boolean.class).write(writer, value). What do you think?

Also, these 3 parsing methods still work on strings: getEnumValue, getEnumSetValue and getByteArrayValue. What do you think about these? The first 2 methods depend on a ValuedEnumParser. I don't think it will be possible to handle those via Gson. getByteArrayValue, on the other hand, should be possible to handle via a TypeAdapter, I think.

[baywet]

getting really close! I think there's still some work needed around the intersection and union types.

[baywet]

Thank you for making the changes!

[baywet]

@papegaaij because we're shipping to be compatible with android as well, there are some "new" java features we can't use.
One of them is the diamond <>, the type needs to be passed explicitly instead.
Would you mind making the update please?

[baywet]

Thank you for making the changes!

[baywet]

@papegaaij this test is now failing because it has a dependency on the JSON serialization infrastructure. Would you mind having a look please?

kiota-java/components/serialization/multipart/src/test/java/com/microsoft/kiota/serialization/MultipartSerializationWriterTests.java

Line 64 in 9decb26

void writesAStructuredObject() throws IOException {

[baywet]

Thank you for making the changes!