feat: Suggestion view pt.2 #293
No reviewers
Labels
No labels
automation
backend
bug
contributor experience
data
deployment
documentation
duplicate
good first issue
help wanted
nice to have
notifications
package maintainer
performance
skin
tech debt
user story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-community/nix-security-tracker#293
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "suggestion-view"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes https://github.com/Nix-Security-WG/nix-security-tracker/issues/203
Closes https://github.com/Nix-Security-WG/nix-security-tracker/issues/210
Some better rendering for package versions.
It's a wrong assumption, there are multiple containers, but we shall only select the most relevant one
Can the channel analyzing logic be moved in its own functions and possibly a utility file for channel analysis?
Definetly, this entire logic is way too noisy for the view.
Any idea how to figure out the most relevant one?
https://github.com/Nix-Security-WG/nix-security-tracker/issues/294
https://github.com/Nix-Security-WG/nix-security-tracker/issues/295
Hmm… I need to think, but basically you need to select the first container containing a package name or containing a CVSS vector string, this sort of stuff.
Maybe, the backend should do more preprocessing to make this palatable.
This is probably wrong but I ended up moving this into the models for now? I thought it might make sense, as the function operates on the types in the
nix_evaluation
model.This might be actually solved by your intermediate representation of merged CVEs, right?
correct!