Specify the API in more modern ways #24
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
waldiTM
force-pushed
the
redefine-api
branch
from
38c35da to
fd53052
Compare
It turns out, we can't make the API compatible with NIST NVD. The definition requires COUNT and OFFSET, which a normal database can never do efficient. So we don't need to care. Also add an initial OpenAPI spec for the API.
waldiTM
force-pushed
the
redefine-api
branch
from
fd53052 to
92ebca5
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.
What this PR does / why we need it:
It turns out, we can't make the API compatible with NIST NVD. The definition requires COUNT and OFFSET, which a normal database can never do efficient. So we don't need to care.
Also add an initial OpenAPI spec for the API.