| Commit message (Collapse) | Author | Lines | ||
|---|---|---|---|---|
| 2022-12-18 | fix Zig's nit comments | -4/+6 | ||
| 2022-12-04 | do not use name mangling in _attach_persistent_roles_view | -2/+2 | ||
| 2022-12-04 | use follow.send to send the role update message | -1/+1 | ||
| 2022-12-04 | edit view through interaction.response.edit_message | -18/+5 | ||
| 2022-12-04 | relay the newly created view to __attach_persistent_roles_view | -8/+15 | ||
| 2022-12-04 | ditch prepare_self_assignable_roles_view by constructing the buttons inside ↵ | -21/+9 | ||
| the view itself | ||||
| 2022-12-04 | make SELF_ASSIGNABLE_ROLES_MESSAGE more inviting for people to interact with | -1/+5 | ||
| 2022-12-04 | update custom id of the AllSelfAssignableRolesView's button | -1/+1 | ||
| 2022-12-04 | use button decorator instead of subclassing discord.ui.Button | -20/+10 | ||
| This will help clarify the relationship between the button & the viw since it'll only be used there | ||||
| 2022-12-03 | rename #Roles section to #Information | -1/+1 | ||
| 2022-12-03 | call super without referencing the current class | -1/+1 | ||
| 2022-12-03 | do not use name mangling | -3/+3 | ||
| This also renames to method to align more with our fetch or {action} pattern | ||||
| 2022-11-27 | make the roles view ephemeral when sent in roles channel | -1/+2 | ||
| 2022-11-27 | add docstrings to RoleButtonView | -6/+17 | ||
| This documents the attributes the class has, which gives better context for future readers/contributors | ||||
| 2022-11-27 | misc style & doc improvements | -3/+3 | ||
| 2022-11-27 | remove waring in setup docstrings | -1/+1 | ||
| 2022-11-27 | rename the method that attaches the persistent view | -4/+12 | ||
| This also enhances the docstrings for a better clarification of its purpose | ||||
| 2022-11-27 | update docs for the newly added view & button | -2/+2 | ||
| 2022-11-27 | Update return.md (#2325) | -11/+8 | ||
| Made the tag more brief without any substantial changes to its overall approach. Co-authored-by: wookie184 <[email protected]> | ||||
| 2022-11-27 | rename prepare_available_role_subscription_view to ↵ | -3/+3 | ||
| prepare_self_assignable_roles_view | ||||
| 2022-11-27 | fix docstrings of the ShowAllSelfAssignableRolesButton's callback function | -1/+1 | ||
| 2022-11-27 | update message content of the persistent view | -2/+2 | ||
| The messages were intended for a button that will automatically assign all availables roles to the interactor This changes since it's not the intended behavior | ||||
| 2022-11-27 | rename ClaimAllSelfAssignableRolesButton to ShowAllSelfAssignableRolesButton | -5/+5 | ||
| 2022-11-27 | include Thread & PrivateChannel in get_or_fetch_channel return types | -1/+3 | ||
| 2022-11-27 | Don't close already closed posts | -0/+6 | ||
| 2022-11-27 | restore original value of DELETE_MESSAGE_AFTER | -1/+1 | ||
| 2022-11-27 | rely on original_message to delete view once it times out | -66/+62 | ||
| 2022-11-26 | add implementation of the button's callback that'll handle assigning the ↵ | -0/+34 | ||
| appropriate roles | ||||
| 2022-11-26 | add assignable_roles as a property to the ClaimAllSelfAssignableRoles button | -3/+4 | ||
| 2022-11-26 | add the logic for attaching the persistent view | -1/+36 | ||
| This comes with another dependency to try to locate the message that needs to hold the view. If that message is not found, a new one will be created & sent. | ||||
| 2022-11-26 | add the AllSelfAssignableRolesView and its corresponding ↵ | -1/+21 | ||
| ClaimAllSelfAssignableRolesButton button Note that these are still dummy views & have no behavior | ||||
| 2022-11-26 | add the roles channel to the config | -0/+5 | ||
| 2022-11-26 | Catch case where starter message is deleted before pinning | -2/+4 | ||
| 2022-11-26 | Update CODEOWNERS | -1/+0 | ||
| 2022-11-26 | Ensure constants.Channels.help_system_forum is a forum channel on load | -1/+3 | ||
| 2022-11-26 | Listen for thread starter on_message rather than thread_create | -10/+19 | ||
| thread_create events are triggered before the thread's starter message is available, so listening for starter messages with on_message instead ensures we have a message object to use. | ||||
| 2022-11-26 | Auto archive help forum posts after inactivity | -1/+78 | ||
| I decided to keep the archive logic simple, and just go for 30 minutes since last message, rather than the hybrid of 30 mins + 10 depending on who sent the last message. The reason for using the hybrid approach previously was due to us running out of channels frequently Since this is no longer a problem, I decided to keep the logic simple. | ||||
| 2022-11-26 | Don't load the help channel cog if disabled | -0/+7 | ||
| 2022-11-26 | Consistantly refer to help posts as posts, not threads | -47/+47 | ||
| 2022-11-26 | Get, and store, the help forum channel object on cog load | -4/+9 | ||
| 2022-11-26 | Ignore Discord errors when clearing snekbox reactions | -2/+3 | ||
| These errors can be caused by the message being deleted, or the message being in an archived thread | ||||
| 2022-11-26 | Update botcore module name | -59/+59 | ||
| 2022-11-26 | Bump all deps to latest | -403/+303 | ||
| 2022-11-26 | Bump bot-core version | -232/+236 | ||
| 2022-11-26 | Refactor Thread Error Catching | -17/+17 | ||
| Co-authored-by: Boris Muratov <[email protected]> Co-authored-by: Amrou Bellalouna <[email protected]> Signed-off-by: Hassan Abouelela <[email protected]> | ||||
| 2022-11-26 | Handle Images As Starter Messages | -1/+5 | ||
| In the case of an image or other media as the starter message, the formatted message in the help DM will be empty, which is invalid for the embed. We populate the field with some more useful text in this case. Signed-off-by: Hassan Abouelela <[email protected]> | ||||
| 2022-11-26 | Check If Thread Is Closed In Pagination | -55/+38 | ||
| Similar to 555ed4e9, the pagination utility needs to catch when it's trying to act on an archived thread. Signed-off-by: Hassan Abouelela <[email protected]> | ||||
| 2022-11-26 | Check If Thread Is Closed In wait_for_deletion | -1/+8 | ||
| The wait_for_deletion utility would try to remove reactions from a message after the timeout expires, which would normally be fine. In threads however, they can be closed while waiting for the timeout to expire. In such a case, the bot will try to remove the reactions after the channel has been closed and fail. A special exception was added for this case to do nothing, since this is only a QoL feature. Signed-off-by: Hassan Abouelela <[email protected]> | ||||
| 2022-11-26 | Catch Failure In Pining Help Starter Message | -2/+7 | ||
| The old method for detecting deleted opener messages does not seem to work, probably because the message is fetched from a cache or similar. Instead we simply try/except pinning the message and pass if the pinning failed. Signed-off-by: Hassan Abouelela <[email protected]> | ||||
| 2022-11-26 | Don't Remove Cooldown Role From Non-Existing Users | -0/+9 | ||
| We try to remove the cooldown role from users before checking if the user is still in the server, which can cause an error since the thread object will just contain `None` as the user. Signed-off-by: Hassan Abouelela <[email protected]> | ||||