-
Notifications
You must be signed in to change notification settings - Fork 599
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
Encode timestamps in RFC3339 #2665
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! A few review concerns:
- This PR changes the signatures of public-facing functions and is therefore breaking. As such, it should target the
next
branch rather thancurrent
. - According to Discord's docs, the
List Joined Private Archived Threads
endpoint expects thebefore
parameter to be a snowflake rather than a timestamp. Since we're dealing with threads here, I thinkChannelId
would be the right type to use. - You've missed an endpoint here, in particular the
List Private Archived Threads
endpoint, which actually does expect a formatted timestamp.
34b5d8e
to
932871c
Compare
932871c
to
fc994aa
Compare
Thank you for your review 🙏 I rebased on the |
Ah, sorry for not being clear enough. It's only the |
fc994aa
to
0b91c89
Compare
Oups, sorry! I just fixed this an squashed the commits. |
This PR fixes #2664, but I am unsure if it should be unwrapped. It would be better to output an error if we cannot encode them. Also, please tell me if it is ok to encode in RFC3339 instead of ISO 8601.