Are there any plans to decouple serialModule from ...

# serialization

[altavir]

Are there any plans to decouple serialModule from serialization engine?

[sandwwraith]

Can you elaborate more on this? You mean removing val serialModule: SerialModule from Encoder interface? Or something else?

[altavir]

I encountered several cases in framework development, where I need to gather serialization module during runtime and could have different serialization modules depending on which program modules are loaded. Right now it seems a little bit unreasonable that I have to declare the specific module inside Json object initialization.

[altavir]

Also we already discussed the cases with tree-like object serialization when serial module is more like a property of serializer than the serialization engine.

[sandwwraith]

So, you expect modules to be available somewhere statically?

[altavir]

Yes, the modules are stored separately from the engine and they are somehow coupled to actual serializers. Right now, I need to build module from parts and create a Json instance for each serialization

[altavir]

Probably the most flexible way is to provide serial module both in the serializer itself and in the global engine and merge them on use.

[sandwwraith]

Why do you need new json instance for each serialization? Each serialization uses different module?

[altavir]

Yes, it is possible that serialization modules will be loaded dynamically. Of course, I can cache them. Still, I have definition of serializers in one place and the actual serialization in the other place. Right now I need to duplicate the information about descendants in two places. I made a workaround by dumping manually dumping the serial module, but I do not like this solution.

[altavir]

It seems to me that the searializer should know about the serial module it exposes/

[altavir]

Specifically in case of tree-like structures