-
Notifications
You must be signed in to change notification settings - Fork 39
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
✨ Takedown policy association #261
Conversation
> | ||
<ActionDurationSelector | ||
action={modEventType} | ||
onChange={(e) => { |
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.
This is unrelated to the objective of this PR but wanted to add it in since it's been requested by mods a few times in the past.
@@ -25,9 +16,10 @@ export const getStaticActions = ({ | |||
shortcut: ['w'], | |||
keywords: 'workspace,panel', | |||
perform: () => { | |||
const newParams = new URLSearchParams(searchParams) | |||
const pathname = window.location.pathname |
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.
this has been causing a bunch of flaky test failures for a while now because of how nextjs was keeping cached version of pathname.
Depends on bluesky-social/atproto#3271
This PR adds a new setting panel for managing a list of policies for takedown action. When taking a subject down moderators can optionally chose a policy from the list to associate with the takedown.
takedown_policy.mov