-
Notifications
You must be signed in to change notification settings - Fork 9.2k
feat: Overlay Calendar v2 and Troubleshooter v2 #14693
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
base: main
Are you sure you want to change the base?
Conversation
@kart1ka is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link. |
📦 Next.js Bundle Analysis for @calcom/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 Seventy-eight Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly 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 Any third party scripts you have added directly to your app using the 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. |
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.
@kart1ka Everything looks good we just have a unit test failing by the looks of things.
Despite the Unit test:
From a UX standpoint this works pretty damn well thanks for this! Tested
- Troubleshooter
- When authed with a gcal - view another user and test overlay calendar
- Signup a new user (had to toggle off overflow and on again) but i honestly think thats in main also.
Code looks pretty good to me - I'd like a second eye by someone with a bit more appstore experience than myself for these changes
@joeauyeung @zomars would you give this a second pair of eyes before we approve?
@sean-brydon Thanks for the review. I have fixed the unit test. Regarding the overflow toggle during signup, you're right—it's present in the main branch too. I've tried to figure out the cause but haven't found a solution yet. |
I am working on adding the Microsoft Provider for overlay user sign up. |
@kart1ka, any update on when this might be ready? Really looking forward to this feature! |
Closing due to staleness. Don't hesitate to re-open when ready! |
@retrogtx Can you please re open this PR? I am working on resolving the conflicts. |
I'm also really excited for this feature. Without event titles the usefulness of the troubleshooter and overlay are significantly limited. |
What does this PR do?
Fixes #12763
Fixes #12752
Type of change
How should this be tested?
Testing Overlay Calendar v2
Testing Troubleshooter v2
Mandatory Tasks