-
-
Notifications
You must be signed in to change notification settings - Fork 734
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
Formatted Invites Parsed Incorrectly #668
Comments
In this case, @averen is right, |
Although, maybe more symbols might be added for further markdown removing. |
Like I mentioned in discord, this is a sloppy solution. All characters outside of the standard 0-9, A-Z, and a-z should be stripped in the same regex expression. Also invites have set lengths depending on their purpose, this should be taken into consideration. |
@averen vanity invites do not have a set length so that cannot be considered. |
That is true, if that isn't allowed in vanity invites I will not allow it in the regex but I have no way of confirming that. It seem as if those formattings aren't intended by discord anyway if you see an embed like that. The better way to do this is |
In that case, this PR should be an appropriate fix. |
General Troubleshooting
Hey there! Before you report a bug or suggest a new feature,
please make sure to follow these steps first!
Issue
Issue Type
Description
When instant invites are formatted using markdown, they are parsed incorrectly and include some markdown characters.
The first message's contents is exactly
__invite__
and the second***invite***
.The text was updated successfully, but these errors were encountered: