Add example with nested segmentation, fix number types, remove extraneous produces#4311
Add example with nested segmentation, fix number types, remove extraneous produces#4311annatisch merged 7 commits intoAzure:masterfrom
produces#4311Conversation
Automation for azure-sdk-for-goA PR has been created for you: |
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-nodeA PR has been created for you: |
Automation for azure-sdk-for-pythonA PR has been created for you: |
Automation for azure-sdk-for-jsA PR has been created for you: |
|
Thanks @alexeldeib - are you able to fix the two failing CI passes? Thanks! |
|
@annatisch Fixed csv formatting for the example, but I have questions about the other issues.
|
|
Still addressing a model validation issue with additionalProperties. |
|
Also have a few unchanged XML request/responses which are now failing CI. The XML is stuffed as a giant string off the response body -- I think when we wrote these examples, this was the only way to incorporate an XML response that worked. Is there a better way to do this? |
|
@annatisch thoughts on above? |
|
Hi @marstr - Do you know what would cause this error in the Go generator? |
|
Hi @lmazuel - do you know if there have been changes to how XML data is represented in Swagger examples? Samples like this one are now failing: Error: |
Ah yeah, the output path configured for the Azure SDK for Go must be in the "services/preview" folder because this spec is in the |
|
Thanks @marstr! Additionally I've confirmed with @sergey-shandar that the model validation errors with regards to XML can be ignored for now. |
|
@marstr I think this is due to #3084 creating the preview/stable folders. When the spec was originally introduced, there were no folders to differentiate stable/preview. What's the preferred solution for you? I can update the path here but you'll end up with a redundant version of the SDK in azure-sdk-for-go. @annatisch thanks for clarifying. I think I covered the other issues with examples, let me know if I missed anything. e: did fix the Go configuration, so waiting for that to finish. |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
* [Nginx] Add certificate API * Fix * Fix 2 * Fix 3
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger