feat: webhook URL parse #221
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: jolheiser <john.olheiser@gmail.com>
topi314
reviewed
Dec 17, 2022
topi314
reviewed
Dec 17, 2022
Co-authored-by: ToπSenpai <15636011+TopiSenpai@users.noreply.github.com>
topi314
reviewed
Dec 17, 2022
Co-authored-by: ToπSenpai <15636011+TopiSenpai@users.noreply.github.com>
topi314
approved these changes
Dec 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Considering Discord doesn't show you the webhook URL and has you copy it as-is, this is a convenience func for parsing a webhook URL wholesale.
As far as I know, they come in the form
https://discord.com/api/webhooks/123456789123456789/foo(without an API version), at least in from the UI, so this somewhat naively assumes that splitting the URL should yield the ID/token in the 3/4 index respectively.An alternative would be to instead do a backwards grab of the last two indexes rather than assume 3/4.
Let me know if you'd prefer that instead.