feat: start implementing useFormat including OSV #225
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
|
close #196 |
| StandardizeKind | ||
| } from "./standard/index.js"; | ||
|
|
||
| export function formatVulnsPayload(format: BaseStrategyFormat = "Preserve") { |
There was a problem hiding this comment.
I wonder if we should keep Preserve format.
We could have only Standard & OSV. If the user wanna "preserve" then he just give undefined or null format (which would be the default), wdyt ?
There was a problem hiding this comment.
Yes could be a good idea (however depend on the implementation because I think we use that type in multiple location).
Anyway in the long term standard should dissapear in favor of OSV (which is the real open source standard).
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.
No description provided.