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
fix: v2 create schedule with availabilities #14551
Conversation
Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 4 Ignored Deployments
|
|
||
if (parts.length !== 3) { | ||
throw new BadRequestException(`Invalid ${key} format. Expected format: HH:MM:SS. Received ${value}`); | ||
throw new BadRequestException( | ||
`Invalid time format. Expected format(ISO8061): 2025-0412T13:17:56.324Z. Received: ${value}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels like for availabilities that are usually on the 0 second we should return back something like that.
e.g. 2025-0412T13:00:00Z
or 2025-0412T13:30:00Z
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not even sure our system can support saving availabilities and then using those availabilities to calculate slots with times like these
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked payload of when availability is updated and "Save" is hit:
And then I matched behaviour exactly in the PR code above - availability atom sends start and end time in the ISO8061 format. There are more elegant ways to write this input DTO but need to think about it and potentially refactor how the availability atom works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that ISO format is definitely the one we want to support but what I was referring to is the date itself. The UI doesn’t support setting your availability down to the second.
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (04/12/24)1 reviewer was added to this PR based on Keith Williams's automation. |
📦 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! 🙌 |
Current Playwright Test Results Summary✅ 310 Passing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 04/12/2024 03:48:44pm UTC) Run DetailsRunning Workflow PR Update on Github Actions Commit: 4e1d469 Started: 04/12/2024 03:44:08pm UTC
|
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
pro user -- legacy Time slots should be reserved when selected
Retry 1 • Initial Attempt |
0% (0)0 / 336 runsfailed over last 7 days |
10.12% (34)34 / 336 runsflaked over last 7 days |
📄 apps/web/playwright/profile.e2e.ts • 2 Flakes
Top 1 Common Error Messages
|
2 Test Cases Affected |
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Update Profile Can add a new email as a secondary email
Retry 1 • Initial Attempt |
0.60% (2)2 / 331 runsfailed over last 7 days |
0.60% (2)2 / 331 runsflaked over last 7 days |
Update Profile Newly added secondary email should show as Unverified
Retry 1 • Initial Attempt |
0.91% (3)3 / 331 runsfailed over last 7 days |
7.25% (24)24 / 331 runsflaked over last 7 days |
📄 apps/web/playwright/availability.e2e.ts • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Availablity Schedule listing
Retry 1 • Initial Attempt |
0% (0)0 / 341 runsfailed over last 7 days |
0.29% (1)1 / 341 runflaked over last 7 days |
📄 packages/embeds/embed-core/playwright/tests/action-based.e2e.ts • 8 Flakes
Top 1 Common Error Messages
|
8 Test Cases Affected |
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Popup Tests should open embed iframe on click - Configured with light theme
Retry 1 • Initial Attempt |
0% (0)0 / 330 runsfailed over last 7 days |
63.94% (211)211 / 330 runsflaked over last 7 days |
Popup Tests should be able to reschedule
Retry 1 • Initial Attempt |
-177.97% (-210)-210 / 118 runsfailed over last 7 days |
177.97% (210)210 / 118 runsflaked over last 7 days |
Popup Tests should open Routing Forms embed on click
Retry 1 • Initial Attempt |
-177.97% (-210)-210 / 118 runsfailed over last 7 days |
177.97% (210)210 / 118 runsflaked over last 7 days |
Popup Tests Floating Button Popup Pro User - Configured in App with default setting of system theme should open embed iframe according to system theme when no theme is configured through Embed API
Retry 1 • Initial Attempt |
-176.27% (-208)-208 / 118 runsfailed over last 7 days |
177.97% (210)210 / 118 runsflaked over last 7 days |
Popup Tests Floating Button Popup Pro User - Configured in App with default setting of system theme should open embed iframe according to system theme when configured with 'auto' theme using Embed API
Retry 1 • Initial Attempt |
-181.03% (-210)-210 / 116 runsfailed over last 7 days |
181.03% (210)210 / 116 runsflaked over last 7 days |
Popup Tests Floating Button Popup Pro User - Configured in App with default setting of system theme should open embed iframe(Booker Profile Page) with dark theme when configured with dark theme using Embed API
Retry 1 • Initial Attempt |
-181.03% (-210)-210 / 116 runsfailed over last 7 days |
181.03% (210)210 / 116 runsflaked over last 7 days |
Popup Tests Floating Button Popup Pro User - Configured in App with default setting of system theme should open embed iframe(Event Booking Page) with dark theme when configured with dark theme using Embed API
Retry 1 • Initial Attempt |
-181.03% (-210)-210 / 116 runsfailed over last 7 days |
181.03% (210)210 / 116 runsflaked over last 7 days |
Popup Tests prendered embed should be loaded and apply the config given to it
Retry 1 • Initial Attempt |
-181.03% (-210)-210 / 116 runsfailed over last 7 days |
181.03% (210)210 / 116 runsflaked over last 7 days |
📄 apps/web/playwright/integrations-stripe.e2e.ts • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Stripe integration Pending payment booking should not be confirmed by default
Retry 1 • Initial Attempt |
1.53% (5)5 / 327 runsfailed over last 7 days |
23.24% (76)76 / 327 runsflaked over last 7 days |
📄 packages/embeds/embed-core/playwright/tests/inline.e2e.ts • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Inline Iframe Inline Iframe - Configured with Dark Theme
Retry 1 • Initial Attempt |
0.60% (2)2 / 331 runsfailed over last 7 days |
53.17% (176)176 / 331 runsflaked over last 7 days |
There was a refactor so validation for schedule availabilities changed. Previously create-availability.input.ts expected for startTime and endTime time in format "HH:mm:ss" but now we are submitting ISO8061 time format e.g. 2025-0412T13:17:56.324Z from the atom.
Driveby: remove permissions from public event-types endpoint
To test i submitted to "http://localhost:5555/api/v2/schedules"
and got response: