-
Notifications
You must be signed in to change notification settings - Fork 207
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
Do we really support application/xml? #2055
Comments
We support the generation of models. However we don't have serialization and deserialization implementations today. |
FYI I've removed those mime types from the default supported ones in #2078 |
I am happy with this change. I don't believe we need to have inbox support for XML. |
@darrelmiller is there documentation around creating and registering custom serializers for Kiota that you could share? Our team has just hit a situation where we wanted to use Kiota proxies with a XML-based API. From your comment above, I assume creating a serializer for XML and plugging it in should be a supported extension point. |
For serialization you would need to implement these two interfaces.
For deserialization
Once this is done, you will register the serializer and deserializer as is done here with the client and you should be able to make requests. You can also checkout the example implementation for form serialization here for inspiration. https://github.com/microsoft/kiota-dotnet/tree/main/src/serialization/form |
The default value for
--structured-mime-types
includes the following:Do we really support serialization of application/xml? Are the text/yaml and text/xml processed by the text serializer? Does the method signature accept/return as a string?
The text was updated successfully, but these errors were encountered: