Evented architecture for moderation system #1617
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| { | ||
| "lexicon": 1, | ||
| "id": "com.atproto.admin.getModerationStatuses", | ||
bnewbold marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| "defs": { | ||
| "main": { | ||
| "type": "query", | ||
| "description": "View moderation statuses of subjects (record or repo).", | ||
| "parameters": { | ||
| "type": "params", | ||
| "properties": { | ||
| "subject": { "type": "string" }, | ||
|
There was a problem hiding this comment. similar to other subject fields, maybe format=uri? |
||
| "note": { | ||
| "type": "string", | ||
| "description": "Search subjects by keyword from notes" | ||
| }, | ||
| "reportedAfter": { | ||
| "type": "string", | ||
| "format": "datetime", | ||
| "description": "Search subjects reported after a given timestamp" | ||
| }, | ||
| "reportedBefore": { | ||
| "type": "string", | ||
| "format": "datetime", | ||
| "description": "Search subjects reported before a given timestamp" | ||
| }, | ||
| "reviewedAfter": { | ||
| "type": "string", | ||
| "format": "datetime", | ||
| "description": "Search subjects reviewed after a given timestamp" | ||
| }, | ||
| "reviewedBefore": { | ||
| "type": "string", | ||
| "format": "datetime", | ||
| "description": "Search subjects reviewed before a given timestamp" | ||
| }, | ||
| "includeMuted": { | ||
| "type": "boolean", | ||
| "description": "By default, we don't include muted subjects in the results. Set this to true to include them." | ||
| }, | ||
| "reviewState": { | ||
| "type": "string", | ||
| "description": "Specify when fetching subjects in a certain state" | ||
| }, | ||
| "limit": { | ||
| "type": "integer", | ||
| "minimum": 1, | ||
| "maximum": 100, | ||
| "default": 50 | ||
| }, | ||
| "cursor": { "type": "string" } | ||
| } | ||
| }, | ||
| "output": { | ||
| "encoding": "application/json", | ||
| "schema": { | ||
| "type": "object", | ||
| "required": ["subjectStatuses"], | ||
| "properties": { | ||
| "cursor": { "type": "string" }, | ||
| "subjectStatuses": { | ||
| "type": "array", | ||
| "items": { | ||
| "type": "ref", | ||
| "ref": "com.atproto.admin.defs#subjectStatusView" | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am interested to hear a little more about how to think about these two fields as a part of action metadata.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
resolveReportIdswill go away since we don't need to keep track of individual reports being resolved.reportTypewill stay and store the metadata for#reportevents only where the user specifies thereportTypeon the client.