chore: use the most recent openapi spec #102
Merged
Conversation
This file contains 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
ecshreve
changed the title
This is the output of npm run bundle-swagger in the api repository. The only manual change made after copying the file was removing the contents of the info.description field.
ecshreve
force-pushed
the
ecs/update-openapi-spec
branch
from
20edb90 to
db18ee2
Compare
|
needed 5e-bits/5e-srd-api#621 |
bagelbits
approved these changes
Dec 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR replaces the openapi.json with the spec generated by
npm run bundle-swaggerin the api repository.The only manual change made after copying the file was, removing the contents of the info.description field.
Note
Not a technical dependency, but should wait until the 5e-bits/5e-srd-api#620 lands before merging this.
details: 5e-bits/5e-srd-api#619