-
Couldn't load subscription status.
- Fork 867
Protocol tests issue 33 #3267
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
Protocol tests issue 33 #3267
Conversation
generator/ServiceClientGeneratorLib/Generators/Marshallers/RestXmlResponseUnmarshaller.tt
Outdated
Show resolved
Hide resolved
| return locationName.ToString(); | ||
| } | ||
| var memberTarget = member.Shape.data[ServiceModel.LocationNameKey]; | ||
| if(member.Shape.data != null && memberTarget != null) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
member.Shape.data != null doesn't seem needed as you would have referenced a location in a null json object previously and that would have failed. Does the check need to be moved or removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're right, Member.Shape.data would never actually return null I removed it
generator/ServiceClientGeneratorLib/Generators/Marshallers/RestXmlResponseUnmarshaller.tt
Outdated
Show resolved
Hide resolved
generator/ServiceClientGeneratorLib/Generators/Marshallers/RestXmlResponseUnmarshaller.tt
Outdated
Show resolved
Hide resolved
|
There are some additional generated changes that snuck in there. These are files that I didn't push in a different commit. You can ignore those. Once we merge all these in we are going to have to run the generator again anyways. |
Description
This PR fixes DOTNET-7357 issue 33.
Issue 33 Issue unmarshalling Xml Responses due to improper handling of "LocationName"MERGE into
protocol-testsfeature branch onlyBuilds on prior PR: #3266
Merge order: 112 (I'm going to start mine from 100 and increment to keep separate from Bo's)
Ticket: DOTNET-7357
Motivation and Context
Testing
N/A - the test cases are the protocol tests. A final dry-run will be done on the
protocol-testsfeature branch once everything is merged into the feature branch.Screenshots (if appropriate)
Types of changes
Checklist
License