fix: datacatalog model validation errors#6831
Merged
yungezz merged 1 commit intoAzure:masterfrom Aug 15, 2019
Merged
Conversation
In Testing, Please Ignore[Logs] (Generated from 3591405, Iteration 3)
|
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. |
Contributor
|
Can one of the admins verify this patch? |
Remove null body and headers for RESPONSE_SCHEMA_NOT_IN_SPEC errors
nschonni
force-pushed
the
fix--datacatalog-model-validaiton-errors
branch
from
6a8aebf to
3591405
Compare
nschonni
changed the title
Member
|
HI @anuchandy could you pls review this PR? |
yungezz
approved these changes
Aug 15, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove null body and headers for RESPONSE_SCHEMA_NOT_IN_SPEC errors