Skip to content

Fix/send responses everywhere customInputs were being sent.#7898

Merged
hariombalhara merged 12 commits intomainfrom
fix/send-responses-everywhere
Apr 4, 2023
Merged

Fix/send responses everywhere customInputs were being sent.#7898
hariombalhara merged 12 commits intomainfrom
fix/send-responses-everywhere

Conversation

@hariombalhara
Copy link
Copy Markdown
Member

@hariombalhara hariombalhara commented Mar 23, 2023

What does this PR do?

Adds responses everywhere customInputs was being sent earlier

Environment: Production

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How should this be tested?

  • Test different scenarios like Request Reschedule(Email, Calendar, WEbhook) Reschedule(Email, Calendar, WEbhook), Cancellation(Email, Calendar, WEbhook), Reminder Emails

Checklist

  • I haven't added tests that prove my fix is effective or that my feature works

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 23, 2023

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

Name Status Preview Comments Updated (UTC)
cal-com-web ❌ Failed (Inspect) Apr 3, 2023 0:43am
dhe ❌ Failed (Inspect) Apr 3, 2023 0:43am
2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
cal ⬜️ Ignored (Inspect) Apr 3, 2023 0:43am
ui ⬜️ Ignored (Inspect) Visit Preview Apr 3, 2023 0:43am

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 23, 2023

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 233.33 KB (-19 B)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Seven Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/apps/[slug]/[...pages] 392.37 KB 625.7 KB 178.77% (🟡 +0.05%)
/event-types 349.33 KB 582.66 KB 166.47% (🟡 +0.05%)
/event-types/[type] 383.16 KB 616.48 KB 176.14% (🟡 +0.03%)
/settings/my-account/appearance 171.3 KB 404.63 KB 115.61% (+/- <0.01%)
/settings/teams/[id]/appearance 171.32 KB 404.65 KB 115.61% (🟡 +0.01%)
/workflows 164.93 KB 398.26 KB 113.79% (🟢 -0.02%)
/workflows/[workflow] 294.1 KB 527.42 KB 150.69% (+/- <0.01%)
Details

Only 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 next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

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.

@@ -14,7 +14,6 @@ type BookingSelect = {
};
};
location: true;
smsReminderNumber: true;
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

wasn't needed


const booking = {
...bookingRaw,
responses: bookingResponsesDbSchema.parse(bookingRaw.responses),
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

No need to parse here. getCalEventResponses can handle the parsing itself now.

}
}
return { calEventUserFieldsResponses, calEventResponses };
return { userFieldsResponses: calEventUserFieldsResponses, responses: calEventResponses };
Copy link
Copy Markdown
Member Author

@hariombalhara hariombalhara Mar 28, 2023

Choose a reason for hiding this comment

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

This renaming allows us to simply spread over the return value to build cal event.

@deploysentinel
Copy link
Copy Markdown

deploysentinel bot commented Mar 28, 2023

Current Playwright Test Results Summary

✅ 66 Passing - ⚠️ 2 Flaky

Run may still be in progress, this comment will be updated as current testing workflow or job completes...

(Last updated on 04/03/2023 12:58:54pm UTC)

Run Details

Running Workflow PR Update on Github Actions

Commit: f61d85e

Started: 04/03/2023 12:53:31pm UTC

⚠️ Flakes

📄   apps/web/playwright/event-types.e2e.ts • 1 Flake

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Event Types tests user can add multiple organizer address
Retry 1Initial Attempt
1.70% (3) 3 / 176 runs
failed over last 7 days
31.25% (55) 55 / 176 runs
flaked over last 7 days

📄   packages/app-store/routing-forms/playwright/tests/basic.e2e.ts • 1 Flake

Test Case Results

Test Case Last 7 days Failures Last 7 days Flakes
Routing Forms Seeded Routing Form Routing Link - Reporting and CSV Download
Retry 1Initial Attempt
9.21% (14) 14 / 152 runs
failed over last 7 days
24.34% (37) 37 / 152 runs
flaked over last 7 days

View Detailed Build Results


@hariombalhara hariombalhara marked this pull request as ready for review March 28, 2023 14:36
@hariombalhara hariombalhara requested a review from zomars as a code owner March 28, 2023 14:36
@hariombalhara hariombalhara requested a review from a team March 28, 2023 14:36
@hariombalhara hariombalhara changed the title Fix/send responses everywhere Fix/send responses everywhere customInputs were being sent. Mar 28, 2023
Copy link
Copy Markdown
Member

@CarinaWolli CarinaWolli left a comment

Choose a reason for hiding this comment

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

It's also missing for the endpoint to test our zapier trigger. It's this endpoint: https://github.com/calcom/cal.com/blob/main/packages/app-store/zapier/api/subscriptions/listBookings.ts

Could you add that too?

@PeerRich
Copy link
Copy Markdown
Member

inform user when merged: https://app.intercom.com/a/inbox/z9l4o9ru/inbox/admin/5018200/conversation/64?view=List

@hariombalhara
Copy link
Copy Markdown
Member Author

@CarinaWolli Thanks !! I have added it at that place also now.

Copy link
Copy Markdown
Member

@CarinaWolli CarinaWolli left a comment

Choose a reason for hiding this comment

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

LGTM! I pushed a change to add userFieldsResponses to the Zapier payload. Will approve after pr-progress.md is removed

Copy link
Copy Markdown
Member

@CarinaWolli CarinaWolli left a comment

Choose a reason for hiding this comment

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

Nice, looking good now 🙌🏻

@hariombalhara hariombalhara merged commit e504f5c into main Apr 4, 2023
@hariombalhara hariombalhara deleted the fix/send-responses-everywhere branch April 4, 2023 04:59
@PeerRich PeerRich added the core area: core, team members only label Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core area: core, team members only

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants