Feat: openapi schema #1
Open
Conversation
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
gremat
force-pushed
the
feat/openapi-schema
branch
14 times, most recently
from
17506cc to
cd15ce8
Compare
gremat
force-pushed
the
feat/openapi-schema
branch
from
cd15ce8 to
80b7b24
Compare
secDre4mer
reviewed
Jan 26, 2026
| information about the running THOR instance. | ||
| version: 1.0.0 | ||
| servers: | ||
| - url: http://localhost:8080/api/v1 |
There was a problem hiding this comment.
We have api/... below as well, so as it is joined to api/v1/api/...
gremat
force-pushed
the
feat/openapi-schema
branch
from
80b7b24 to
113ee7f
Compare
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.
Release process is working in general, see my test tag v0.1.0 and the related release. See also the resulting GitHub Pages page: https://nextronsystems.github.io/thunderstorm-openapi/index.html . Yet the pipeline is shown as failed, I don't know why the tag pipelines are associated with the PR. I'll try to resolve this after the approval, and will clean up after the merge and push a new v1.0.0 tag.