Skip to content
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

feat(status-roles): add cog to assign roles based on user status #789

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

electron271
Copy link
Contributor

@electron271 electron271 commented Mar 24, 2025

Description

add automatically giving roles based on status

Guidelines

  • My code follows the style guidelines of this project (formatted with Ruff)

  • I have performed a self-review of my own code

  • I have commented my code, particularly in hard-to-understand areas

  • I have made corresponding changes to the documentation if needed

  • My changes generate no new warnings

  • I have tested this change

  • Any dependent changes have been merged and published in downstream modules

  • I have added all appropriate labels to this PR

  • I have followed all of these guidelines.

How Has This Been Tested? (if applicable)

ran it with regex "test" and changed status

Summary by Sourcery

Adds a cog that automatically assigns roles to users based on their status, using regular expressions to match against the user's custom status. The cog checks and updates roles on startup and when a user's presence changes.

New Features:

  • Introduces a cog that automatically assigns roles to users based on their status.
  • Adds a configuration option to define status-to-role mappings using regular expressions.
  • The cog checks and updates roles on startup and when a user's presence changes.
  • Adds logging for role assignments, removals, and errors related to status role automation.

@electron271 electron271 requested a review from kzndotsh March 24, 2025 00:16
Copy link
Contributor

sourcery-ai bot commented Mar 24, 2025

Reviewer's Guide by Sourcery

This pull request introduces a new cog, StatusRoles, that automatically assigns and removes roles from users based on their custom Discord status. It reads configuration from CONFIG.STATUS_ROLES, which defines the mapping between regular expressions and role IDs. The cog listens for presence updates and periodically checks all members to ensure their roles match their current status.

Sequence diagram for status role assignment

sequenceDiagram
    participant User
    participant DiscordClient
    participant StatusRolesCog
    participant DiscordAPI

    User->>DiscordClient: Updates status
    DiscordClient->>StatusRolesCog: on_presence_update(before, after)
    StatusRolesCog->>StatusRolesCog: get_custom_status(member)
    StatusRolesCog->>StatusRolesCog: has_activity_changed(before, after)
    StatusRolesCog->>StatusRolesCog: check_and_update_roles(member)
    StatusRolesCog->>StatusRolesCog: get_custom_status(member)
    StatusRolesCog->>StatusRolesCog: for each config in STATUS_ROLES
    StatusRolesCog->>StatusRolesCog: re.search(pattern, status_text)
    alt matches and not has_role
        StatusRolesCog->>DiscordAPI: member.add_roles(role)
        DiscordAPI-->>StatusRolesCog: Role added
    else not matches and has_role
        StatusRolesCog->>DiscordAPI: member.remove_roles(role)
        DiscordAPI-->>StatusRolesCog: Role removed
    end
Loading

File-Level Changes

Change Details Files
Introduced a new cog to manage roles based on user status.
  • Created StatusRoles cog with listeners for on_ready and on_presence_update.
  • Implemented check_and_update_roles to add or remove roles based on status regex matching.
  • Added get_custom_status to extract custom status text from a member's activities.
  • Included error handling for invalid regex patterns and permission issues.
  • Added logging for role assignments, removals, and errors.
tux/cogs/services/status_roles.py
Added a new configuration parameter for status roles.
  • Added STATUS_ROLES to the Config class to store status role configurations.
  • Updated Config initialization to load STATUS_ROLES from the config file.
tux/utils/config.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @electron271 - I've reviewed your changes - here's some feedback:

Overall Comments:

  • Consider adding a more specific exception handler for discord.Forbidden to differentiate between missing permissions to add vs remove roles.
  • It might be helpful to include the server ID in the log messages for easier debugging.
Here's what I looked at during the review
  • 🟡 General issues: 1 issue found
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟡 Complexity: 1 issue found
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines +66 to +67
# Status Roles
STATUS_ROLES: Final[list[dict[str, int]]] = config["STATUS_ROLES"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Consider revising the type annotation for STATUS_ROLES.

The current type annotation suggests that all dictionary values are ints, yet later the code retrieves a regex pattern string from the config. It may be more precise to revise the annotation (or use a TypedDict) to reflect that some values are strings.

Suggested implementation:

from typing import Union
    STATUS_ROLES: Final[list[dict[str, Union[int, str]]]] = config["STATUS_ROLES"]

Ensure that the import for "Union" is added only once at the top of the file if there are multiple typing imports.


return None

async def check_and_update_roles(self, member: discord.Member):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (complexity): Consider extracting helper functions to reduce nesting and improve the readability and testability of the check_and_update_roles function by separating the per-config processing, regex matching, and role update logic into their own methods .

Consider extracting helper functions to break down the nested logic in check_and_update_roles. For example, you can separate the per-config processing, regex matching, and role update into their own methods. This keeps each function focused and easier to test. For instance:

def status_matches(self, status_text: str, pattern: str) -> bool:
    """Check if the status text matches the provided regex pattern."""
    return bool(re.search(pattern, status_text, re.IGNORECASE))

Then refactor the role update logic:

async def update_member_role(self, member: discord.Member, role: discord.Role, should_have: bool, pattern: str, status_text: str):
    if should_have and role not in member.roles:
        logger.info(f"Adding role {role.name} to {member.display_name} (status: '{status_text}' matched '{pattern}')")
        await member.add_roles(role, reason="Status role automation")
    elif not should_have and role in member.roles:
        logger.info(f"Removing role {role.name} from {member.display_name} (status no longer matches)")
        await member.remove_roles(role, reason="Status role automation")

Finally, simplify check_and_update_roles by looping through configs and delegating per-config processing:

async def check_and_update_roles(self, member: discord.Member):
    if member.bot:
        return

    status_text = self.get_custom_status(member) or ""
    for config in self.status_roles:
        if int(config.get("server_id", 0)) != member.guild.id:
            continue

        role_id = int(config.get("role_id", 0))
        pattern = str(config.get("status_regex", ".*"))
        role = member.guild.get_role(role_id)
        if not role:
            logger.warning(f"Role {role_id} configured in STATUS_ROLES not found in guild {member.guild.name}")
            continue

        try:
            matches = self.status_matches(status_text, pattern)
            await self.update_member_role(member, role, matches, pattern, status_text)
        except re.error:
            logger.exception(f"Invalid regex pattern '{pattern}' in STATUS_ROLES config")
        except discord.Forbidden:
            logger.exception(f"Bot lacks permission to modify roles for {member.display_name} in {member.guild.name}")
        except Exception:
            logger.exception(f"Error updating roles for {member.display_name}")

These changes maintain all functionality while reducing nesting and improving readability and testability.

Comment on lines +53 to +57
for activity in member.activities:
if isinstance(activity, discord.CustomActivity) and activity.name:
return activity.name

return None
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (code-quality): Use the built-in function next instead of a for-loop (use-next)

Suggested change
for activity in member.activities:
if isinstance(activity, discord.CustomActivity) and activity.name:
return activity.name
return None
return next(
(
activity.name
for activity in member.activities
if isinstance(activity, discord.CustomActivity) and activity.name
),
None,
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant