-
Notifications
You must be signed in to change notification settings - Fork 2
feat: using open-payments-specifications submodule #2
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
Conversation
🦋 Changeset detectedLatest commit: 8c4d3d6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
raducristianpopa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know the README is not updated yet, but I assume it is planned to do this in a later PR - git commands to initialize and download the submodule when cloning the repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remind me why do we need to publish the OpenAPI specs alongside the SDK?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To validate the responses from the API calls, using createOpenAPI from the openapi package
Changes proposed in this pull request
open-payments-specificationsas a submodule, pinning to v1.0.2 of the specsContext
Closes NOD-1