snippetunban ¶
Snippet unban moderation command.
This module provides functionality to remove snippet bans from Discord members. It integrates with the moderation case tracking system.
Classes:
-
SnippetUnban–Discord cog for snippet unban moderation commands.
Functions:
-
setup–Set up the SnippetUnban cog.
Classes¶
SnippetUnban ¶
SnippetUnban(bot: Tux)
Bases: ModerationCogBase
Discord cog for snippet unban moderation commands.
This cog provides the snippetunban command which restores a member's ability to create snippets in the server.
Initialize the SnippetUnban cog.
Parameters:
-
bot(Tux) –The bot instance to attach this cog to.
Methods:
-
snippet_unban–Remove a snippet ban from a member.
-
moderate_user–Execute moderation action using the service architecture.
-
is_jailed–Check if a user is jailed.
-
is_pollbanned–Check if a user is poll banned.
-
is_snippetbanned–Check if a user is snippet banned.
-
get_config–Get a configuration value from CONFIG with support for nested keys.
-
__repr__–Return a string representation of the cog instance.
-
unload_if_missing_config–Check if required configuration is missing and log warning.
Attributes:
-
db(DatabaseCoordinator) –Get the database coordinator for accessing database controllers.
Attributes¶
db property ¶
db: DatabaseCoordinator
Get the database coordinator for accessing database controllers.
Returns:
-
DatabaseCoordinator–Coordinator providing access to all database controllers.
Examples:
>>> await self.db.guild_config.get_guild_config(guild_id)
>>> await self.db.cases.create_case(...)
Notes
This property provides convenient access to database operations without needing to access self.bot.db directly.
Functions¶
snippet_unban async ¶
snippet_unban(ctx: Context[Tux], member: Member, *, flags: SnippetUnbanFlags) -> None
Remove a snippet ban from a member.
Parameters:
-
ctx(Context[Tux]) –The context object.
-
member(Member) –The member to remove snippet ban from.
-
flags(SnippetUnbanFlags) –The flags for the command. (reason: str, silent: bool)
moderate_user async ¶
moderate_user(
ctx: Context[Tux],
case_type: CaseType,
user: Member | User,
reason: str,
silent: bool = False,
dm_action: str | None = None,
actions: Sequence[tuple[Any, type[Any]]] | None = None,
duration: int | None = None,
**kwargs: Any,
) -> None
Execute moderation action using the service architecture.
Parameters:
-
ctx(Context[Tux]) –Command context
-
case_type(CaseType) –Type of moderation action
-
user(Member | User) –Target user
-
reason(str) –Reason for the action
-
silent(bool, default:False) –Whether to suppress DM to user, by default False
-
dm_action(str | None, default:None) –Custom DM action description, by default None
-
actions(Sequence[tuple[Any, type[Any]]] | None, default:None) –Discord API actions to execute, by default None
-
duration(int | None, default:None) –Duration in seconds for temporary actions, by default None
-
**kwargs(Any, default:{}) –Additional case data
_setup_command_usage ¶
_setup_command_usage() -> None
Generate usage strings for all commands in this cog that lack explicit usage.
The generated usage follows the pattern: <qualified_name> <param tokens>
Where: - Required parameters are denoted as <name: Type> - Optional parameters are denoted as [name: Type] - The prefix is intentionally omitted (provided by ctx.prefix)
Examples:
ban <member: Member> [reason: str] config set <key: str> <value: str>
Notes
Respects explicit usage strings if already set on a command. Errors during generation are logged but don't prevent cog loading.
is_jailed async ¶
_generate_usage ¶
Generate a usage string with support for flags and positional parameters.
This method inspects the command's callback signature to detect: - FlagConverter parameters (e.g., --flag value) - Positional parameters (e.g., <required> or [optional])
Parameters:
-
command(Command) –The command to generate usage for.
Returns:
-
str–Generated usage string, or qualified command name as fallback.
Notes
Delegates to shared usage generator for consistency across all cogs. Falls back gracefully to command name if generation fails.
is_pollbanned async ¶
is_snippetbanned async ¶
get_config ¶
Get a configuration value from CONFIG with support for nested keys.
Parameters:
-
key(str) –The configuration key to retrieve. Supports dot notation for nested values (e.g.,
"BOT_INFO.BOT_NAME"). -
default(Any, default:None) –Default value to return if key is not found, by default None.
Returns:
-
Any–The configuration value or default if not found.
Examples:
>>> self.get_config("BOT_INFO.BOT_NAME")
'Tux'
>>> self.get_config("MISSING_KEY", "fallback")
'fallback'
Notes
Errors during retrieval are logged but don't raise exceptions. Returns the default value on any error.
__repr__ ¶
__repr__() -> str
Return a string representation of the cog instance.
Returns:
-
str–String representation in format
<CogName bot=BotUser>.
unload_if_missing_config ¶
Check if required configuration is missing and log warning.
This allows cogs to detect missing configuration at load time and return early from init to prevent partial initialization.
Parameters:
-
condition(bool) –True if config is missing (should unload), False otherwise.
-
config_name(str) –Name of the missing configuration for logging purposes.
Returns:
-
bool–True if config is missing (caller should return early), False if config is present.
Examples:
>>> def __init__(self, bot: Tux):
... super().__init__(bot)
... if self.unload_if_missing_config(not CONFIG.GITHUB_TOKEN, "GITHUB_TOKEN"):
... return # Exit early, cog will be partially loaded but won't register commands
... self.github_client = GitHubClient()
Notes
When this returns True, the cog's init should return early to avoid initializing services that depend on the missing config. The cog will be loaded but commands won't be registered properly, preventing runtime errors.
For complete cog unloading, the bot owner should remove the cog from the modules directory or use the reload system to unload it programmatically.
_unload_self async ¶
_unload_self(extension_name: str) -> None
Perform the actual cog unload operation.
Parameters:
-
extension_name(str) –Full extension name to unload.
Notes
This is called as a background task by unload_if_missing_config(). Errors during unload are logged but don't raise exceptions.