-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
fix: corrected discord link pattern #8612
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@hiteshbedre is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
📦 Next.js Bundle Analysis for @calcom/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
@Udit-takkar any update on this? |
@hiteshbedre reviewing it now |
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.
LGTM
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.
Thank you for the contribution @hiteshbedre 🙏 I missed it in my earlier review.
What does this PR do?
Discord link such as
https://www.discordggg/
is also getting validated correctly with current pattern.Problem:
So I corrected the escape pattern and also replaced
*
with+
at the end, which mandates the character after end slash.Fixes and improves: #8182
Screen.Recording.2023-05-02.at.1.43.45.AM.mov
Environment: Staging(main branch) / Production
Type of change
How should this be tested?