-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advisory "revision"/"release" date #519
Comments
@ctron So what I get from this is that you want the search only to search by the advisory_current rather than both advisory_current and cve_release? Maybe we can split this into two separate qualifiers instead, advisory_current and cve_release? Rather than mixing them. Then if you really want to search both one can use an OR |
Sounds good! |
We have a column "revision" in the advisory result table. We want to sort & filter by this. The idea is to give the user "a set of recently changed documents".
Revision is actually this:
trustification/spog/ui/src/components/advisory/mod.rs
Line 71 in a31c97d
Which seems to come from this:
trustification/spog/api/src/advisory.rs
Line 97 in a31c97d
Which seems to come from this:
trustification/vexination/index/src/lib.rs
Line 463 in a31c97d
Which seems to be the "current release" date:
trustification/vexination/index/src/lib.rs
Lines 150 to 153 in a31c97d
However, searching by "release" brings up weird results. I assume this is due to the fact that
Release
, does a bit more:trustification/vexination/index/src/lib.rs
Lines 692 to 703 in a31c97d
Couldn't we have a single "release" date, which carries the "last modified" date? (defaulting to the initial date if that isn't present).
The text was updated successfully, but these errors were encountered: