Conversation
Continue the migration started with createPaymentRequest so all non-legacy payment request endpoints render from a single source of truth, keeping request, response and error docs consistent.
Spectral oas3-valid-media-example requires amount as string and conditionId as integer to match the payment-activity schema.
The mdoc page was a thin shell of openApiEndpoint tags around content that now lives in the spec. Generating the page, navigation and search entries from the spec removes the duplication so endpoint, model and error docs have a single source of truth.
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
1 participant
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.
Continues the migration started with createPaymentRequest so all non-legacy payment request endpoints render from a single source of truth.
Verified with eslint, vitest (69 passed), ref resolution check, and mdoc operationId coverage.