Align the OpenAPI spec with the written spec#139
Merged
Conversation
Signed-off-by: Matthias Lechner <matlec.public@gmail.com>
phil-abb
approved these changes
Feb 26, 2026
ajcraig
approved these changes
Feb 26, 2026
Contributor
|
@phil-abb and I approve of these changes to ensure consistency between Specification docs and OpenAPI specification. |
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
3 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.
Description
This relates to margo/sandbox#208. The current OpenAPI specification is not aligned with the written specification. This PR aligns the OpenAPI specification with the (more recent) written specification.
Issues Addressed
Please refer to margo/sandbox#208 for a comprehensive list of all misalignments.
Change Type
Please select the relevant options:
Checklist