After pull request #30 When the EventScheduler function schedule_events(self) is called it gives the following error:

/home/paulmolczanski/playground/Discord-Bot/src/__main__.py:83: RuntimeWarning: coroutine 'Loop.__call__' was never awaited self.schedule_events() RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Steps to reproduce:

1. Set up .env
2. Setup credentials.json
3. Remove restriction that schedule_events(self) can only be run at 6 am

User types a command asking people if they would like to join the study group by replying to the event with yes it would create a time for designated users to join the study group chat letting people organize themselves easily

What is the feature you would like to request?

With the discord.py library abandoned , it would be ideal to move the codebase over to a library with support and maintenance. In the future, changes such as Slash Commands and inability to read messages without approved intent will cause Bots using the library to stop working.

As a proactive step in keeping this project functional, migration over to another Python Discord library is required. Luckily there is a fork of the old library called Pycord. It is actively maintained and supports new API features which I and other contributors have had to implement manually. These features include "slash commands, context menus, scheduled events, timeouts, and others."

EDIT: This migration to Pycord should utilize its ~~alpha version~~ recently released beta-version if we want to have access to these new API features.

pip uninstall discord.py
pip install py-cord==2.0.0b1

After reading various articles and Discord developer blogs, the deadline to make this migration before the loss of Bot functionality is April 2022.

How would this feature work?

Based on the Quick Examples section in the PyCord README.md and Bot sample, very little of our actual codebase has to change. The code we currently have could be migrated over without difficulty.

We could even refactor some of our code (such as event scheduling) to use the new API features in PyCord. After making these changes, amendments to the current documentation will need to be made to reflect the use of the new library.

Major Changes

• Improved handling of study group titles and special characters in titles.
• Added docstrings for !help command
• Added !version command to see the current version.
  • Releases will be tagged with a version for all future releases.

Minor Changes

• Minor formatting fixes
• Refactored sheet_parser.py to be more reusable.

TODO:

I have done my best to check for bugs and possible security vulnerabilities, but I am definitely imperfect. Those who I've requested a review from if you could give this release a thorough once over so that we don't have to do any more frantic bug fixes that would be much appreciated. Ideally, this pull request can be reviewed and merged by tomorrow morning.

Possibly have a feature that has the user say a topic for example sql then it goes through the free code camp tutorials and gives back a video for that topic or if not free code camp just a top rated youtube video

We used google spreadsheets throughout semester one to keep track of all of our assignments and tests but making a bot to do it for us is a lot more efficient! Our beginning objective is to make the bot automatically list events that will show what classes we have for the week and what room they are in. This will let students click the event tab and see what time the class is, what room it's in, and a description of what we're going to be learning

Features

• Automatically add events (Date, class, room number, description...)
• Let people interact with the event in case class is postponed or canceled

Any other ideas feel free to add them below!

by typing !list courses, the bot sends all the courses in the semester with their name and course code by typing !list courses=comp, the bot sends all the COMP courses, same with !list courses=math and sending the MATH courses

Theres still some cleaning up to do in regards to the logic and error handling messages if the user gives an invalid message, which ill touch up at a later date, just wanted to get this out for some base functionality

Describe the bug...

When calling !list for one of our classes, the Bot repeats the header of the first class twice.

To Reproduce...

Detail the steps to reproduce the behavior:

1. Call !list all

2. Note the unexpected behavior.

3. Call !list COMP1006

4. Note the unexpected behavior,

Expected Behavior

The heading should only show up once for every class.

As the Bot expands it is important to make command options transparent to the user. A custom help command would mean centralizing general information about commands into the help function.

The descriptions should be concise, but convey necessary information about using the bot to the user.

While I only briefly reviewed this code it may be of some help.

To make creating issues easier, to make and read. It would be useful to create templates/checklist for different kinds of issues, bug reports, and pull requests.

For example, a pull request template could be:

1. What is the purpose of the pull request?
2. Is this feature or fix complete? (otherwise, a separate branch will be created for it)
3. Does your code compile?
4. Have you added the appropriate tags?

In the long run, this will help streamline interactions and will allow for less wasted time trying to figure out what a person is trying to do or say.

We need a profile picture for the bot. If you have a suggestion for a profile please leave a comment here. After reviewing the submitted assets we'll pick one and integrate it into the next version!

Bumps certifi from 2021.10.8 to 2022.12.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

What is the feature you would like to request?

In order to make monitoring of the bot easier it would be beneficial to have a dedicated log channel on the discord available to admins to easily see logs of the bot.

How would this feature work?

The log outputs in the script would have to be pipped somehow into a text channel. Specifics still unknown.

What is the feature you would like to request?

Instead of @everyone for morning announcements it would be more useful to have it specific to the year each person is in on the discord. For example, year one students would be tagged with @year1 vs year 2 students would get an announcement starting with @year2. This would help give more useful information to people without clogging up their notifications.

How would this feature work?

Based on which part of the spreadsheet the announcement is coming from the bot would use the correct @ for the students (e.g. @year1, @year2, @year3, @year4)

OPTIONAL: What part of the Pycord framework can we use to solve this problem?

This shouldn't require any extra usage of Pycord.

Notes

Every student would be given a tag based on which year they are in and the spread sheet would have to be modified to accommodate multiple student years course loads

Now that there's integration for both classes and assignments I think the next step is allowing for those events and/or assignments to be modified with commands. After doing some research there appears to be built-in command parsing for the discord.py library. Command group documentation Video explanation

I'm not quite sure how the commands structure would be arranged or perhaps subcommands aren't even necessary. An idea that comes to mind could be a structure like so: !delay {Assignment name} {number of days delayed}

In addition, if the command gets let's say 5 thumbs up reactions (this number could be adjusted) the google sheet is adjusted to reflect the change.