You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love to combine the power of storing data as json or jsonb and providing a custom manifest that is not the class name (because that is likely to change.
Currently I cannot wrap my head around how to do that, since once I enable my JsonEncoder to be used, I can no longer provide a manifest.
I would like to include the the version of the event either in the manifest or, potentially even better in the tags as ('version', '1.0').
The text was updated successfully, but these errors were encountered:
Okay, I read the code and while I think it would still be nice to support this version via the manifest, there is also another way I could come up with to support versioning and adapters for versions:
package sample.product.events.v1
case class ProductOrdered extends Versioned("v1") (....)
And then using that version once I need to write an adapter from an old version to the new version. The type will have to remain in place for deserialization to work, but that's probably not even bad, because it is very explicit.
I would love to combine the power of storing data as
json
orjsonb
and providing a custom manifest that is not the class name (because that is likely to change.Currently I cannot wrap my head around how to do that, since once I enable my
JsonEncoder
to be used, I can no longer provide a manifest.I would like to include the the version of the event either in the manifest or, potentially even better in the tags as
('version', '1.0')
.The text was updated successfully, but these errors were encountered: