added text labels to the API and the backend #60
Merged
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.
Adds the ability for frontends to send text labels to the backend to be stored.
The idea is this, for example, when a user stumbles across a text that contains profanity, they can flag that to their frontend, which will send it to the backend. Text labels can be associated with a post ID, but do not have to be. We currently provide a list of labels in
protocol -> TextLabel
, but this is up to change. Labels are submitted with a score from 0.0 to 1.0. Not every label must be present in the sent data.