ModerationCase entity #7614
ModerationCase entity #7614
Conversation
isoos
commented
Apr 4, 2024
isoos
commented
- New moderation and report processing flow #7535
- not in use yet, just the implementation of the specification
| /// - `moderation-upheld`, if this is an appeal (kind = appeal) of a notification | ||
| /// where we applied content moderation, and we decided to uphold that decision. | ||
| /// - `moderation-reverted`, if this is an appeal (kind = appeal) of a notification | ||
| /// where we applied content moderation, and we decided to revert that decision. |
There was a problem hiding this comment.
Perhaps document the null case.
There was a problem hiding this comment.
Maybe we shouldn't allow null? E.g. pending could indicate the in-progress state, and it is also possible to filter for it...
There was a problem hiding this comment.
IF we want a pending thing, we should rename it status.
For querying it's probably fine to have a pending value.
This does not have any API-exposed use case, there is no need to generate JSON serialization. |
| /// - `moderation-upheld`, if this is an appeal (kind = appeal) of a notification | ||
| /// where we applied content moderation, and we decided to uphold that decision. | ||
| /// - `moderation-reverted`, if this is an appeal (kind = appeal) of a notification | ||
| /// where we applied content moderation, and we decided to revert that decision. |
There was a problem hiding this comment.
IF we want a pending thing, we should rename it status.
For querying it's probably fine to have a pending value.
Co-authored-by: Jonas Finnemann Jensen <jopsen@gmail.com>
Maybe it is better to reduce the possible values to |
