Fix settings_global API documentation: separate GET and POST paths #2280
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.
The OpenAPI spec incorrectly documented both GET and POST operations under
/settings_global.json, but the actual implementation uses different paths.Changes
/settings_global.jsonpath to contain only the GET operation/settings_globalpath for the POST operationImplementation vs Documentation
Actual endpoints (script/rvd_front):
The OpenAPI spec now matches this implementation with two distinct path entries.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.