-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Update media type for JSON Patch #62988
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
@ECHO OFF | ||
SET RepoRoot=%~dp0..\.. | ||
SET RepoRoot=%~dp0..\..\.. | ||
%RepoRoot%\eng\build.cmd -projects %~dp0**\*.*proj %* |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -507,6 +507,28 @@ | |
} | ||
} | ||
} | ||
}, | ||
"/schemas-by-ref/json-patch": { | ||
"patch": { | ||
"tags": [ | ||
"Sample" | ||
], | ||
"requestBody": { | ||
"content": { | ||
"application/json-patch+json": { | ||
"schema": { | ||
"$ref": "#/components/schemas/JsonPatchDocumentOfParentObject" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It seems like we need a custom JSON convert to model the schema for JSON path document. I assume the schema looks something like:
@mikekistler Sanity checking this by you. Does it seem sufficient to use the same schema for all JsonPatchDocument types or should we figure out some way to capture the properties of the model that you're patchinmg in the schema? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If needed I could look into doing that in a follow-up, as that's existing behaviour anyway without the media type change. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually, the "JsonPatchDocumentOfParentObject": { }, I think we can tackle the issue of the patch body schema in a separate PR. We should probably open an issue for this. I don't have an issue with using the same schema for all patch operations, but it should be more like the schema you show above. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK, sounds good. We can probably add special handling for the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
} | ||
} | ||
}, | ||
"required": true | ||
}, | ||
"responses": { | ||
"200": { | ||
"description": "OK" | ||
} | ||
} | ||
} | ||
} | ||
}, | ||
"components": { | ||
|
@@ -599,6 +621,7 @@ | |
} | ||
} | ||
}, | ||
"JsonPatchDocumentOfParentObject": { }, | ||
"LocationContainer": { | ||
"required": [ | ||
"location" | ||
|
Uh oh!
There was an error while loading. Please reload this page.