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

❓ Decide to implement a daily or weekly check about chat data #16

Closed
MasterCruelty opened this issue Apr 17, 2024 · 0 comments · Fixed by #21
Closed

❓ Decide to implement a daily or weekly check about chat data #16

MasterCruelty opened this issue Apr 17, 2024 · 0 comments · Fixed by #21
Assignees
Labels
enhancement New feature or request medium priority if it can be fixed early, it's better Refactor Refactored something

Comments

@MasterCruelty
Copy link
Owner

In the beginning I thought it would be a Telegram app that you can run sometimes when you would like to see data trend about personel chat. Basically you start the python process, do your stuff and then kill it.


Instead now I guess it could be more interesting if it run 24/7 such as a normal bot application, so it can do a check automatically in a specific range of days or weeks.

In this last case, the function already exists new_check_chat_data. It needs only to be scheduled. Maybe the user can decide by himself the range of schedule.

@MasterCruelty MasterCruelty added enhancement New feature or request Refactor Refactored something medium priority if it can be fixed early, it's better labels Apr 17, 2024
@MasterCruelty MasterCruelty self-assigned this Apr 17, 2024
MasterCruelty added a commit that referenced this issue Aug 3, 2024
@MasterCruelty MasterCruelty linked a pull request Aug 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request medium priority if it can be fixed early, it's better Refactor Refactored something
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant