Skip to content
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

[CAL-4951] Add a testing/dry run banner in dry-run mode of booking(identified isBookingDryRun) #18426

Closed
hariombalhara opened this issue Dec 31, 2024 · 1 comment
Labels
booking-page area: booking page, public booking page, booker 🧹 Improvements Improvements to existing features. Mostly UX/UI

Comments

@hariombalhara
Copy link
Member

Intention is to clearly show to the user when he lands on the page that it is a test page or a dry run booking page.

From SyncLinear.com | CAL-4951

@hariombalhara hariombalhara changed the title [CAL-4951] Add a testing/dry run banner in dry-run mode of booking [CAL-4951] Add a testing/dry run banner in dry-run mode of booking(identified isBookingDryRun) Dec 31, 2024
@dosubot dosubot bot added booking-page area: booking page, public booking page, booker 🧹 Improvements Improvements to existing features. Mostly UX/UI labels Dec 31, 2024
@vaibhav0725
Copy link

Approach For Resolving The Issue

  1. creating a reusable banner [DryRunBanner.tsx] as a component for the frontend section (ui)
  2. next, implementing a flag [isBookingDryRun] keeping it false initially
  3. fetching value[true/false : accordingly] for it through the api route, and display/not display the banner accordingly
  4. creating a backend api to support all the above

Lemme Know

  • if I am understanding the issue correctly
  • and if yes, then please provide me some insights about how to proceed

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 🧹 Improvements Improvements to existing features. Mostly UX/UI
Projects
None yet
Development

No branches or pull requests

2 participants