Skip to content

fix: correct booker email input #21077

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

sean-brydon
Copy link
Member

@sean-brydon sean-brydon commented May 2, 2025

What does this PR do?

CleanShot 2025-05-02 at 08 56 01

Uses the correct component in booker instead of the routing forms widgets


Summary by mrge

Fixed the booker email input to use the correct input component instead of the routing form widget. This ensures proper handling of email values in the form.

@sean-brydon sean-brydon requested a review from hariombalhara May 2, 2025 07:58
@graphite-app graphite-app bot requested a review from a team May 2, 2025 07:58
@keithwillcode keithwillcode added consumer core area: core, team members only labels May 2, 2025
@dosubot dosubot bot added the booking-page area: booking page, public booking page, booker label May 2, 2025
@@ -205,7 +205,16 @@ export const Components: Record<FieldType, Component> = {
if (!props) {
return <div />;
}
return <Widgets.TextWidget type="email" id={props.name} noLabel={true} {...props} />;
Copy link
Member Author

Choose a reason for hiding this comment

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

We use input field in the rest of this components file - not sure why we used widget here.

@hariombalhara
Copy link
Member

It affects both Routing Form field and Booker field right?

Copy link

graphite-app bot commented May 2, 2025

Graphite Automations

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

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

"Add ready-for-e2e label" took an action on this PR • (05/02/25)

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

Copy link

@mrge-io mrge-io bot left a comment

Choose a reason for hiding this comment

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

mrge reviewed 1 file and found no issues. Review this PR in mrge.io.

@sean-brydon
Copy link
Member Author

sean-brydon commented May 2, 2025

It affects both Routing Form field and Booker field right?

Yes but the one thats rendered in the form not the form builder that uses a different set of components

cal.com/packages/app-store/routing-forms/components/react-awesome-query-builder/widgets.tsx The RAQB form builder uses these components where as the components rendered in booker/forms use the components in

cal.com/packages/features/form-builder/Components.tsx

Copy link
Contributor

github-actions bot commented May 2, 2025

E2E results are ready!

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 consumer core area: core, team members only ready-for-e2e
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants