-
Notifications
You must be signed in to change notification settings - Fork 9
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
adds fedocal support #33
base: main
Are you sure you want to change the base?
Conversation
Thanks so much for the PR! Just thinking, I have been trying to use the subcommands to logically group our commands. Not 100% sold on this, but maybe something like:
and then just do the alias thing similar to what we do here: Lines 52 to 63 in e508639
itll be a lot simpler, just a straight alias to !nextmeetings and !nextmeeting (the idea behind this is to have the aliases more hidden for compatibility purposes i.e. not in the Also, i think we can reduce this down to a single command too (!nextmeeting and !nextmeetings) doing the same thing, being: 1.Show (if any) meetings scheduled for the room the command was called in The idea here being having two seperate commands is a bit of overkill, and just outputting all the info is not that bad, because there is really not that much. |
Adds !nextmeeting and !nextmeetings
I am not entirely sure that the test classes are working 100% for the messages for multi line. Any suggestions appreciated.