Skip to content

Update storybook test patterns to match modern standards#99

Merged
jaruesink merged 2 commits into
codegen-bot/update-calendar-components-latest-shadcnfrom
codegen-bot/update-storybook-test-patterns-a8f3d2
Jun 8, 2025
Merged

Update storybook test patterns to match modern standards#99
jaruesink merged 2 commits into
codegen-bot/update-calendar-components-latest-shadcnfrom
codegen-bot/update-storybook-test-patterns-a8f3d2

Conversation

@codegen-sh
Copy link
Copy Markdown
Contributor

@codegen-sh codegen-sh Bot commented Jun 8, 2025

Summary

Updated all storybook test files to use the modern patterns established in the date-picker and calendar components. This brings consistency across all story tests and improves debugging capabilities.

Changes Made

Import Updates

  • Changed from 'storybook/test' to '@storybook/test'
  • Added within import for proper canvas element querying
  • Updated type imports where needed

Play Function Modernization

  • Updated function signatures from play: async (storyContext) => {} to play: async ({ canvasElement, step }) => {}
  • Added const canvas = within(canvasElement); setup
  • Organized tests into logical steps using await step('Description', async () => {})

Test Organization

Applied step-based structure for better debugging:

  1. "Verify initial state" - Check default component states
  2. "Test interactions" - User interactions and state changes
  3. "Submit and verify" - Form submission and result validation

Files Updated

Simple Toggle Components:

List and Group Components:

Text Input Components:

Complex Interactive Components:

Benefits

  • Consistency: All story tests now follow the same modern patterns
  • Better Debugging: Step-based organization makes it easier to identify test failures
  • Improved Readability: Clear test phases and descriptive step names
  • Future-Proof: Aligned with latest Storybook testing best practices

Testing

All existing test logic has been preserved while updating the structure. The tests should continue to work as before but with improved organization and debugging capabilities.


💻 View my workAbout Codegen

- Update imports from 'storybook/test' to '@storybook/test'
- Add 'within' import for canvas element querying
- Update play function signatures to use destructured parameters
- Add step-based test organization for better debugging
- Preserve existing test logic while modernizing structure
- Apply patterns from date-picker and calendar components

Files updated:
- checkbox.stories.tsx: Added step organization and modern patterns
- switch.stories.tsx: Updated imports and step structure
- checkbox-custom.stories.tsx: Updated imports
- switch-custom.stories.tsx: Updated imports and type fixes
- checkbox-list.stories.tsx: Updated imports and dependencies
- radio-group.stories.tsx: Updated imports and streamlined dependencies
- radio-group-custom.stories.tsx: Updated imports and type fixes
- text-field.stories.tsx: Updated imports
- text-field-custom.stories.tsx: Updated imports and type fixes
- textarea.stories.tsx: Updated imports
- textarea-custom.stories.tsx: Updated imports
- dropdown-menu-select.stories.tsx: Updated imports and dependencies
- otp-input.stories.tsx: Updated imports and dependencies
@bolt-new-by-stackblitz
Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 8, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 8, 2025

📝 Storybook Preview: View Storybook

This preview will be updated automatically when you push new changes to this PR.

Note: The preview will be available after the workflow completes and the PR is approved for deployment.

@jaruesink
Copy link
Copy Markdown
Contributor

jaruesink commented Jun 8, 2025

@codegen-sh my switch customized component is not working as expected, please look into the following error and fix

Unexpected Application Error!
Can't find variable: FormLabel
PurpleLabel@https://lambda-curry.github.io/forms/pr-99/assets/switch-custom.stories-DOk3pZOs.js:1:1902
qn@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:34105
$n@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:61920
W1@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:106243
Eh@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:105344
Ac@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:105182
L1@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:102329
cv@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:24:113610
Aa@https://lambda-curry.github.io/forms/pr-99/assets/react-18-CHiuWb18.js:9:1652
💿 Hey developer 👋
You can provide a way better UX than this when your app throws errors by providing your own ErrorBoundary or errorElement prop on your route.

I'll look into the switch component error for you! 🔧

💻 View my work

- Change FormLabel and FormMessage from type-only imports to actual imports
- This fixes the 'Can't find variable: FormLabel' runtime error
- Components need to be imported as actual values, not just types
@codegen-sh
Copy link
Copy Markdown
Contributor Author

codegen-sh Bot commented Jun 8, 2025

✅ Fixed the switch-custom component error!

The issue was that FormLabel and FormMessage were imported as types only (import type { FormLabel, FormMessage }), but they were being used as actual components in the PurpleLabel and PurpleMessage custom components.

I've changed the import to:

import { FormLabel, FormMessage } from '@lambdacurry/forms/remix-hook-form/form';

This fixes the "Can't find variable: FormLabel" runtime error. The switch-custom component should now work properly! 🎯

🔄 View Updated PR #99 on Github 🔄

💻 View my work • React 👍 or 👎

@jaruesink jaruesink marked this pull request as ready for review June 8, 2025 03:52
@jaruesink jaruesink merged commit c2d6439 into codegen-bot/update-calendar-components-latest-shadcn Jun 8, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant