Closed smw-wagnerma closed 3 years ago
If the code fails to compile for you, that has nothing to do with the workspace definiton. You're right though that macro-utils should be part of the workspace, just pushed a commit adding it there.
Can you describe the actual issue you're seeing more clearly?
I generate the code from my xsd and wsdl files, by the way, works very well, thanks!
Now, I wan't to use the code in a project, so I copy the generated files to the project and then I get compile erros, missing types e.g. xs:: and so on. I try to fix this referenceing the packages containig them in the Cargo.toml:
xsd-types = { git = "https://github.com/lumeohq/xsd-parser-rs", branch = "main" } xsd-parser = { git = "https://github.com/lumeohq/xsd-parser-rs", branch = "main" }
But the macro-utils, which is also needed for the generated code, I cant'reference, because it is not in the workspace definition.
I see. Does it work now after cargo update
?
Yep, now I can reference it, but the usability is tough. I open a seperate issue and close this
The generator creates code with the types UtilsTupleIo and UtilsDefaultSerde:
#[derive(Default, PartialEq, Debug, UtilsTupleIo, UtilsDefaultSerde)]
These types are in macro-utils, but it seems I can't reference it from Cargo.toml, the workspace definition is:
Miss I something?