fix: automation model validation errors#6782
Conversation
nschonni
commented
Jul 30, 2019
- Add "body" for RESPONSE_BODY_NOT_IN_EXAMPLE errors
- "path" -> "folderPath"
- Add "body" for RESPONSE_BODY_NOT_IN_EXAMPLE errors - "path" -> "folderPath"
SDK Automation [Logs] (Generated from 7c45716, Iteration 1)
|
Automation for azure-sdk-for-pythonUnable to detect any generation context from this PR. |
Automation for azure-sdk-for-goUnable to detect any generation context from this PR. |
|
Can one of the admins verify this patch? |
|
@raych1 here are the outstanding errors (I only fixed those ones mentioned in the commit message), just FYI, here are the still failing rules: This one seems like a bug, because a Delete probably shouldn't be returning anything Some missing response bodies in the examples |
|
Thanks @nschonni , there're a few invalid_type errors. Do you know how cause this? |
|
I think Swagger 2 or the current x-ms-example stuff doesn't have a good way to represent file responses in an example. |
|
@nschonni , can we use this PR and add more commits to fix other errors? |
|
Sure if you want. The "allow edits from maintainers" checkbox is on |
|
Sorry, what I meant is will you continue to fix other errors along with this PR? |
|
Ah, no I don't think I can fix any of those other ones. EX: removing the response schema from the deletes would probably be a breaking change, and it could be correct. Also adding the response I'd need to know what they'd look like. |
|
I see, comes back to this PR. What's the reason changing |
|
The property is "folderPath" in the spec rather than "path" Could be a spec error, and I can undo it if you want |
raych1
left a comment
There was a problem hiding this comment.
Looks good to me for the fixes.