Complex and simple types are put in a nested types module.
A module is crates with the snake_case name of the original Struct. This should help avoiding conflicts between different xsds and it also allow auto-use all the needed traits without duplications within the same scope.
The visibility of the derived struct is forwarded to the module, in order to easily export inner structs. Please let me know if this feature is desired or not.
The main problem of this PR is that introduces breaking changes, because the simple and complex types have a different path.
typesmodule.Struct. This should help avoiding conflicts between different xsds and it also allow auto-use all the needed traits without duplications within the same scope.The main problem of this PR is that introduces breaking changes, because the simple and complex types have a different path.
Closes #11