Feat: warn and mute command #142
Conversation
|
@TendTo I'd need to change the settings yaml but there's no placeholder file for default settings, is this behaviour intended? |
Do you mean src/spotted/config/yaml/settings.yaml? |
My bad, I missed from the new documentation the new way of creating your own settings and the absence of a |
Co-authored-by: Stefano Borzì <[email protected]>
…ttedDMI-Bot into feat/warn_command
| user.mute(info.bot) | ||
| text = f"L'utente è stato mutato per {days} giorn{'o' if days == 1 else 'i'}." | ||
| await info.bot.send_message(chat_id=info.chat_id, text=text) | ||
| context.job_queue.run_once(unmute_user, timedelta(days=days), context=user) |
There was a problem hiding this comment.
This job probably gets lost and the user remains muted if, for any reason, the bot gets restarted on the VM.
Just adding a safeguard job running at 5:00 utc could ensure this won't be a problem, but you would have to keep track of the timestamp in a db table
There was a problem hiding this comment.
Yes, I was actually not sure about putting the timedelta in the db table or not, in that case I might as well starting the job_queue on each bot restart rather than checking every day
| warn_expiration = datetime.now() + timedelta(days=Config.post_get("warn_after_days")) | ||
| DbManager.delete_from( | ||
| table_name="warned_users", | ||
| where="warn_time > %s", | ||
| where_args=(warn_expiration,), | ||
| ) |
There was a problem hiding this comment.
It depends on how you implement warn_time, but this should probably be a - and warn_time < %s.
| class IsAdminFilter(MessageFilter): | ||
| """Check if the message from the update was sent by | ||
| one of the administrators of the group | ||
| Args: | ||
| MessageFilter: the superclass for the filter | ||
| """ | ||
|
|
||
| def filter(self, message: Message): | ||
| chat = message.chat | ||
| sender_id = message.from_user.id | ||
| if chat.type in [Chat.SUPERGROUP, Chat.GROUP]: | ||
| return sender_id in [admin.id for admin in chat.get_administrators(chat.id)] | ||
| return False |
There was a problem hiding this comment.
Interesting Filter. It opens quite a few possibilities
| CREATE TABLE IF NOT EXISTS muted_users | ||
| ( | ||
| user_id BIGINT NOT NULL, | ||
| PRIMARY KEY user_id |
|
we could close this for #155 |
Prerequisites
CHANGELOG.rstfile with an overview of the changes made.Description
Adding /warn and /mute command to the bot functionalities
Issue closed by this PR
Does this PR introduce a breaking change?
Python version you are using
Python 3.10.12