Jimmy Hartzell

I wrote #34 . Since then my company has adopted a policy of always using `-R`. Is there any reason to behave the other way? I think it should probably...

Generated code uses `flatten` on i32, though not supported on `yaserde`

2

`zeep` generated this: ``` #[derive(Debug, Default, YaSerialize, YaDeserialize, Clone)] #[yaserde( rename = "portNumber", namespace = "tns: urn:rpm-stateManagementInterface", prefix = "tns", )] pub struct PortNumber { #[yaserde(flatten, default)] pub body: i32,...

Generated SoapError type doesn't implement std::error::Error

3

This is more of a feature request, but it would be easy and nice for the generated error types to implement std::error::Error.

Generated code includes calls to log macros without `use log::*` or similar

2

It shows up with `debug!` and `warn!`, but does not import them, resulting in errors like: ``` error: cannot find macro `debug` in this scope --> src/soap.rs:368:21 | 368 |...

Empty `xs:element` elements result in missing types

2

This works fine: ``` ``` But this results in no type being outputted: ``` ``` Which results in errors: ``` error[E0412]: cannot find type `StateUpdateNotificationResponse` in module `types` --> src/soap.rs:85:32...

Documentation does not specify all deps, dep versions

1

The documentation says the outputted code requires `yaserde`, `reqwest`, and `tokio`. It does not mention that `log`, `yaserde_derive` and `async-trait` are also required. It also does not specify what versions...

Put windows deps in (default-included) feature

9

Due to idiosyncrasies of how cargo resolves dependencies, all the Windows dependencies show up in Cargo.lock files even on Linux -- and in Yocto builds, which is making our build...