-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add report fingerprint functionality #705
Add report fingerprint functionality #705
Conversation
Looks good! Is the idea that the logic for submitting and evaluating reports stays is implemented in the stash tagging interface? |
9b0877e
to
3edc233
Compare
Had to rework this after the fingerprint normalisation.
That's correct. It wouldn't be difficult to add report submission to the UI, but it feels like a potential vector of abuse to me. I have changed the vote input to be an enum instead of an int. Should be ready for review and test. |
Adds a
vote
field to theFingerprintSubmission
input. This supercedes theunmatch
field, which is now deprecated. Ifvote
is positive, then the submission is treated as an ordinary submission. Ifvote
is negative, then the submission is treated as a report. Ifvote
is0
, then it is treated as an unmatch operation. Ifvote
is omitted altogether, then it is assumed to be a normal submission, unlessunmatch
is set to true, per existing behaviour.Adds
reports
field to theFingerprint
type. This value is the number of users that have reported a fingerprint. Also adds auser_reported
field which returns true if the current user reported the fingerprint. Scene fingerprints are now ordered bysubmissions - reports
.The UI is changed to indicate how many reports a fingerprint has. The button to remove a user submission is shown in the appropriate place based on if the user submitted or reported the fingerprint.