Conversation
…ailsSheet Co-Authored-By: unknown <>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
There was a problem hiding this comment.
2 issues found across 1 file
Prompt for AI agents (all issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/web/modules/bookings/components/BookingDetailsSheet.tsx">
<violation number="1" location="apps/web/modules/bookings/components/BookingDetailsSheet.tsx:831">
P2: Custom questions are now hidden entirely when `bookingFields` is undefined, even if `responses` exist. This regresses the previous behavior and can make historical bookings show no custom questions. Consider falling back to rendering `responses` when `bookingFields` is missing.</violation>
<violation number="2" location="apps/web/modules/bookings/components/BookingDetailsSheet.tsx:842">
P2: Boolean responses that are `false` are filtered out by `if (!answer) return null`, so the new Yes/No rendering never shows "No". Adjust the guard to only skip null/undefined (and empty strings) so false values render correctly.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Contributor
Devin AI is addressing Cubic AI's review feedbackNew feedback has been sent to the existing Devin session. ✅ No changes pushed |
hbjORbj
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Applies calcom/cal@07914e6 onto cal.com.
Previously, custom questions in the BookingDetailsSheet were rendered based on the iteration order of
Object.entries(booking.responses), which is arbitrary (JS object key insertion order). This PR changes the iteration to use the event type'sbookingFieldsarray, so custom questions appear in the order configured by the event type author.Changes:
bookingFieldsinstead of responses: The component now maps over thebookingFieldsarray and looks up each field's answer from the responses record, ensuring consistent ordering"true"/"false"validResponsesandfieldLabelsmemoizations since the new single-pass approach is cleanerrecurringInfoternary and added parentheses around nullish coalescing inlocalizedTimezoneMandatory Tasks (DO NOT REMOVE)
How should this be tested?
Important review notes
bookingFieldsis undefined: Previously, responses would still render even withoutbookingFields. Now, ifbookingFieldsis missing, the entire section returnsnull. Reviewers should verify this is acceptable — it could hide responses for edge cases where the event type'sbookingFieldsisn't populated.calcom/cal(the file has minor import differences between repos), so verifying the adaptation is faithful to the original commit is worthwhile.