-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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: fixes multiple storybook stories and updates to the new sb7 format #12683
Conversation
@stabildev 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 to collect XP and win prizes! |
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: @radix-ui/react-select@0.1.1, @storybook/addon-mdx-gfm@7.6.3 |
📦 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! 🙌 |
awesome work I'll take a look more in detail tomorrow |
@@ -48,7 +48,7 @@ describe("Tests for ColorPicker component", () => { | |||
const colorInput = screen.getByRole("textbox"); | |||
await act(async () => userEvent.clear(colorInput)); | |||
const newColorValue = "#00FF00"; | |||
await act(async () => userEvent.type(colorInput, newColorValue)); | |||
await act(async () => await userEvent.type(colorInput, newColorValue)); |
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.
this seems like a recurring issue, this test is quite flaky, do we even need act ?
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.
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.
@testing-library doc is quite explicit that act
should not be necessary, need to double check why we need to chain await like that
<StorybookTrpcProvider> | ||
<TooltipProvider> |
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.
awesome 🔥
@@ -85,6 +89,8 @@ module.exports = { | |||
}, |
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.
what's your opinion on autodocs ?
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.
IMO not needed for Cal.com since all stories have an explicit mdx
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 didn't see any difference when adding or omitting this option so I don't think it matters.
What was your reasoning behind lazy builds?
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.
great work
What does this PR do?
Replacement of #12628 to account for updates made in #12673 by @ThyMinimalDev (cc @emrysal)
TooltipProvider
, see above)useRouter
)Type of change