I've just started to implement this package in a few apps. It's great!
Currently there is support for custom deserialization on QueryConfig (the field is called serializer but I think this is incorrect), but serialization of the query data to json happens within the query storage, expecting toJson to exist.
I'd like to suggest:
moving serializing out of the storage interface and into the query. Each QueryConfig would have the ability to override the default serialization/deserialization.
removing serializer/deserializer from the global QueryConfig. This would require query config and global config separating into 2 different objects. I don't think a global deserializer makes sense and I guess this only currently exists at the global level due to there being one query config
I've just started to implement this package in a few apps. It's great!
Currently there is support for custom deserialization on QueryConfig (the field is called serializer but I think this is incorrect), but serialization of the query data to json happens within the query storage, expecting
toJsonto exist.I'd like to suggest:
serializer/deserializerfrom the global QueryConfig. This would require query config and global config separating into 2 different objects. I don't think a global deserializer makes sense and I guess this only currently exists at the global level due to there being one query config