feat: Added more query params to successRedirect page#8271
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@titanventura 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! 🙌 |
|
Thanks for the support ! I would like to thank @adarsh-a-tw - link who paired with me and helped me raise this PR ! |
|
@sean-brydon Please review. Thanks ! |
📦 Next.js Bundle Analysis for @calcom/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 Five Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
📦 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! 🙌 |
|
Please review ! |
| eventTypeSlug: eventType.slug, | ||
| seatReferenceUid: "seatReferenceUid" in responseData ? responseData.seatReferenceUid : null, | ||
| ...(rescheduleUid && booking?.startTime && { formerTime: booking.startTime.toString() }), | ||
| ...getBookingRedirectExtraParams(responseData), |
There was a problem hiding this comment.
This should be done as part of bookingSuccessRedirect and that fn is called at multiple places as redirections happens from multiple places.
| "startTime", | ||
| "endTime", | ||
| "location", | ||
| ...objectQueryParamKeys, |
There was a problem hiding this comment.
Instead of differentiating manually b/w object and non-object params, we should use the typeof operator to identify the value. This would allow us to maintain a single list.
Also, I would like to keep the list very strict because whatever we expose has to be considered for backward compatibility as websites would rely on those params.
Stable Params - Good to be passed as is
- title
- description
- startTime
- endTime
- location
user and attendees might have different props depending on what we queried. So, we need to pick keys specifically from here. So, it might be better to remove these keys and wait for a requirement from users as to what they use it for.
|
thanks for the suggestions @hariombalhara . Have made the changes. Please review ! |
|
Any updates on this ? |
|
Thank you for following the naming conventions! 🙏 |
|
@titanventura Are you there to review the changes I pushed? I have made the changes to send email as new param I have also ensured that no other query param is sent that isn't in documentation. |
| price: true, | ||
| slug: true, | ||
| length: true, | ||
| offsetStart: true, |
There was a problem hiding this comment.
Why are these changes made in managedEventTypes ?
|
This PR is being marked as stale due to inactivity. |
|
/bonus 20 @titanventura can you take another look at this PR and fix the merge conflicts? <3 |
|
A bonus of $20 has been added by PeerRich. |
hariombalhara
left a comment
There was a problem hiding this comment.
LGTM now !! Thanks @titanventura
|
@titanventura: Your claim has been rewarded! 👉 Complete your Algora onboarding to collect the bounty. |
|
🎉🎈 @titanventura has been awarded $20! 🎈🎊 |
What does this PR do?
Pass extra booking params to redirect URL
Fixes #7802
Edit by @hariombalhara
Right now there is an option to enable sending these query params in this PR.

A sample redirect URL generated using the avove configuration
https://www.google.com/?isSuccessBookingPage=true&email=d%40e.com&eventTypeSlug=abc&title=ABC+between+Team+Pro+Example+and+d&description=sd&startTime=2023-05-12T03%3A45%3A00.000Z&endTime=2023-05-12T04%3A00%3A00.000Z&location=integrations%3Awhereby_videoParams Sent to Custom Success Redirect Page
2023-05-12T03:45:00.000Z)2023-05-12T04:00:00.000Z)integrations:{APPNAME}_videoe.g. integrations:whereby_video. See more possible values for it hereI am of the opinion that we should do it by default and that checkbox isn't required. There is a very edge case where sending a lot of query params can break the URL size limit but we can ignore that for now.
cc @PeerRich @Jaibles
Type of change
Checklist