This repository has been archived by the owner on Jul 16, 2021. It is now read-only.
Add support for x-ms-paths, x-ms-odata, and x-ms-error-response #19
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.
There are two issues with this PR:
assert_json_diff
to allow for empty objects to be treated as though the key is not present.x_ms_odata
key is modeled as anOption<String>
. TheString
in this case is always a reference to another file with the object's definition. Unfortunately, normally references are json objects with one key "$ref", but in this case it's just the string value without the key. We should think about how to unify these difference types of references.This should close #3 though there is still one extension "x-ms-text" which doesn't seem to be in any of the Azure REST spec json files.