pycord icon indicating copy to clipboard operation
pycord copied to clipboard

feat: Add support for Guild Scheduled Event Recurrence

Open DA-344 opened this issue 11 months ago • 2 comments

Summary

Adds support for receiving, setting, and updating a Scheduled Event's recurrence rule.

Documentation: resources/guild-scheduled-event

Needs testing.

Information

  • [ ] This PR fixes an issue.
  • [x] This PR adds something new (e.g. new method or parameters).
  • [ ] This PR is a breaking change (e.g. methods or parameters removed/renamed).
  • [ ] This PR is not a code change (e.g. documentation, README, typehinting, examples, ...).

Checklist

  • [x] I have searched the open pull requests for duplicates.
  • [ ] If code changes were made then they have been tested.
    • [x] I have updated the documentation to reflect the changes.
  • [x] If type: ignore comments were used, a comment is also left explaining why.
  • [x] I have updated the changelog to include these changes.

DA-344 avatar Mar 23 '25 18:03 DA-344

Merge conflicts (complicated discord feature, requires intense testing)

Lulalaby avatar Aug 02 '25 03:08 Lulalaby

@DA-344 went ahead and fixed the merge conflicts for you. please double check

Lulalaby avatar Sep 01 '25 20:09 Lulalaby

Not wanting to be disrespectful or anything, but it’s been some time since this hasn’t been updated or fixed as it’s implementing, if I understand correctly, a wrong/limited usage of schedule event (see Paillat comment). So should we switch in a way to #3025, which also implements this, fixing the current issue with the month days and month numbers? And imo the read only is a bit weird not saying for dpy but in py-cord we pretty much have nothing as read only so it disturb me a bit Since it’s also fixing a bunch of other stuff, overload, etc. (unrelated to guild even recurrence) Please let me now

Lumabots avatar Jan 16 '26 08:01 Lumabots

As I already mentioned somewhere (forgot where) this PR should focus on Event Recurrence, and #3025 should focus on fixing the caching and parsing issues currently present.

@DA-344 Are you still planning to work on this ? There's a couple comments to be addressed.

Paillat-dev avatar Jan 16 '26 10:01 Paillat-dev