Skip to content

feat: implement booking page error boundary#20492

Merged
hbjORbj merged 3 commits intomainfrom
feat/implement-booking-page-error-boundary
Apr 1, 2025
Merged

feat: implement booking page error boundary#20492
hbjORbj merged 3 commits intomainfrom
feat/implement-booking-page-error-boundary

Conversation

@hbjORbj
Copy link
Contributor

@hbjORbj hbjORbj commented Apr 1, 2025

What does this PR do?

  • Left a self review

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • N/A - I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

  • Please use the latest Vercel preview and test please 🙏.

@graphite-app graphite-app bot requested a review from a team April 1, 2025 21:21
@keithwillcode keithwillcode added core area: core, team members only foundation labels Apr 1, 2025
@dosubot dosubot bot added booking-page area: booking page, public booking page, booker ✨ feature New feature or request labels Apr 1, 2025

import { type PageProps } from "@lib/d/[link]/[slug]/getServerSideProps";

import BookingPageErrorBoundary from "@components/error/BookingPageErrorBoundary";
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Client-side errors thrown in Booker will now get caught in BookingPageErrorBoundary

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Errors thrown in RSCs will render:
Screenshot 2025-04-01 at 5 20 33 PM

While client-side errors caught in BookingPageErrorBoundary will render:
Screenshot 2025-04-01 at 5 10 03 PM
Screenshot 2025-04-01 at 5 10 06 PM

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hbjORbj How does it look in a production build?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks the same!

@hbjORbj hbjORbj enabled auto-merge (squash) April 1, 2025 21:23
@vercel
Copy link

vercel bot commented Apr 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
cal ⬜️ Ignored (Inspect) Visit Preview Apr 1, 2025 9:24pm
calcom-web-canary ⬜️ Ignored (Inspect) Visit Preview Apr 1, 2025 9:24pm

@graphite-app
Copy link

graphite-app bot commented Apr 1, 2025

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (04/01/25)

1 reviewer was added to this PR based on Keith Williams's automation.

@hbjORbj hbjORbj merged commit b5b4134 into main Apr 1, 2025
40 of 41 checks passed
@hbjORbj hbjORbj deleted the feat/implement-booking-page-error-boundary branch April 1, 2025 22:13
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2025

E2E results are ready!

emrysal pushed a commit that referenced this pull request Apr 1, 2025
* implement booking page error boundary

* use it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

booking-page area: booking page, public booking page, booker core area: core, team members only ✨ feature New feature or request foundation ready-for-e2e

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants