Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option IndentWsdl to control if the generated WSDL should be indented #1010

Merged
merged 1 commit into from
Feb 7, 2024

Conversation

vidrenning
Copy link
Contributor

@vidrenning vidrenning commented Feb 7, 2024

Currently the option IndentXml can be used to control if the generated XML is indented or not. This applies to both: the SOAP response XML and the generated WSDL.

It would be nice to control both of these independently. For example, the XML for the SOAP responses should not be indented, but the XML for the WSDL should be indented.

I propose to add a new configuration option IndentWsdl. If this option is explicitly set, it will control if the generated WSDL is indented or not. If it is not set, it will default to the setting of IndentXml, so existing users should not notice a difference in behavior.

…nted or not

Removed field _indentWsdl from SoapMessageEncoder. This information is
now directly passed into the WriteMessageAsync method.

The new option IndentWsdl can be used to control if the WSDL should
be indented or not. By default, it uses the same value as IndentXml,
for backwards compatibility.
@andersjonsson
Copy link
Collaborator

Looks good. Thanks!

@andersjonsson andersjonsson merged commit aa687d9 into DigDes:develop Feb 7, 2024
3 checks passed
@vidrenning
Copy link
Contributor Author

Thanks for merging!

@vidrenning vidrenning deleted the indentwsdl branch February 7, 2024 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants