Standardizing and fixing serialization

[Jacob-Steentoft]

Been diving a bit deeper into the library to fix the issues that we're having with the current preview as the serialization process is a bit strange from a normal STJ pattern.

The following changes fixes callbacks having out of order type params and fully supporting serialization and deserialization of all the existing polymorphic types.

Layers is still a bit of a beast due to the way that the properties are setup, but I'll have a pass on the OneOf serialization process to see if we can support the built-in types mixing with normal types.

[Jacob-Steentoft]

Note that this removed the simple type that was created for callbacks. This is a breaking change, but will allow for more data in the future.

[MatejMa2ur]

Does this work without a problem?

[Jacob-Steentoft]

In my testing, yes. The data is returned from MapLibre using the type property, and the type descriminator is FeatureCollection. So STJ can handle everything for us for serial and deserial

[MatejMa2ur]

Hi,
can you please elaborate more about the breaking change on callbacks?

I am mainly asking, because the code seem fine, I just do not fully understand what will be the breaking change.

[Jacob-Steentoft]

Hi, can you please elaborate more about the breaking change on callbacks?

I am mainly asking, because the code seem fine, I just do not fully understand what will be the breaking change.

The SimpleFeature is replaced with another type which can break if people have any dependencies on the type itself. The fix is very quick however as you just need to replace the type reference since the properties are the same.