-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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: #15045 #15094
Fix: #15045 #15094
Conversation
Someone is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details:
|
Graphite Automations"Add community label" took an action on this PR • (05/17/24)1 label was added to this PR based on Keith Williams's automation. "Add foundation team as reviewer" took an action on this PR • (05/17/24)1 reviewer was added to this PR based on Keith Williams's automation. "Add consumer team as reviewer" took an action on this PR • (05/17/24)1 reviewer was added to this PR based on Keith Williams's automation. |
📦 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! 🙌 |
i think this has been fixed |
This PR addresses the issue where the "Terms" link was not rendering in the UI and fixes a linting error due to missing key props in the Trans component from react-i18next.
Changes Made
The "Terms" link was not appearing correctly in the UI.
Updated the Trans component structure to ensure proper rendering of both "Terms" and "Privacy Policy" links in both BookEventForm.tsx and signup.tsx
Added key props to the Link elements within the components array to resolve the linting error (Missing "key" prop for element in array react/jsx-key).