Closed bergmark closed 9 years ago
Another idea here is to release a new regular-xmlpickler
that reuses GXmlPickler
from generic-xmlpickler
. I think we can do this without the possibility of breakage then.
We decided to go the breaking change route and drop regular immediately. Merged as f0484cf
This removes the regular dependency and stuffs.
Before merging this we may want to write tests and verify that generic-xmlpickler is compatible with regular-xmlpickler, perhaps by copying over the json-schema/generic-aeson tests. And we might as well combine it with another major release of rest packages since this doesn't add any functionality but is a breaking change.