-
Notifications
You must be signed in to change notification settings - Fork 2
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
DEV: Move Activity Pub configuration to dedicated admin panel #78
DEV: Move Activity Pub configuration to dedicated admin panel #78
Conversation
@angusmcleod so sorry for the delay here, I'm now ready to review this, but any chance you can address the merge conflict with main? |
@pmusaraj Ready! |
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.
Looks great, made a few cosmetic code changes, but otherwise it's solid, thanks!
@options={{hash | ||
none="admin.discourse_activity_pub.actor.model_type.none" | ||
}} | ||
/> |
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.
For a followup, since we're only going to have one of two options here (a category or a tag), I would prefer a radio button or something else here other than a dropdown. It's fine for now, though.
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.
It's possible there could also be Group (i.e. user group) and even custom Persons (i.e. users) here too. We may not have either, but other actor types are conceivable.
Oh one last thing @angusmcleod, it would be more consistent if the UI for this was under the plugins tab. As in: Hopefully that's not too big of an ask. |
@pmusaraj This moves the ActivityPub settings to a dedicated admin panel, which both prepares us for Tag actors and also improves the Actor CRUD (e.g. the extension to category custom fields is no longer required).