Skip to content

Conversation

@GoldGroove06
Copy link
Contributor

@GoldGroove06 GoldGroove06 commented Jan 19, 2025

BlockQuote color prop with test, docs and storybook

Summary by CodeRabbit

  • New Features

    • Added optional color prop to BlockQuote component for customizing accent color
    • Enhanced documentation with a structured properties table for BlockQuote
  • Documentation

    • Updated documentation to clearly display BlockQuote component properties
  • Tests

    • Added test case to verify color attribute rendering for BlockQuote

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 19, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

docs/app/docs/components/blockquote/page.js

Oops! Something went wrong! :(

ESLint: 8.56.0

ESLint couldn't find the config "next/core-web-vitals" to extend from. Please check that the name of the config is correct.

The config "next/core-web-vitals" was referenced from the config file in "/docs/.eslintrc.json".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

This pull request introduces a color customization feature for the BlockQuote component across multiple files. The changes include adding a new optional color prop to the component's type definition, updating the component to support rendering a data attribute for accent color, enhancing the storybook configuration to demonstrate the new color feature, and adding a corresponding test to validate the color attribute functionality.

Changes

File Change Summary
docs/app/docs/components/blockquote/page.js Added documentation table with columns and data to describe BlockQuote component properties
src/components/ui/BlockQuote/BlockQuote.tsx Added optional color prop and data-accent-color attribute support
src/components/ui/BlockQuote/stories/BlockQuote.stories.js Added new Color story demonstrating color prop usage
src/components/ui/BlockQuote/tests/BlockQuote.test.tsx Added test case to verify color attribute rendering

Sequence Diagram

sequenceDiagram
    participant Component as BlockQuote
    participant Props as Props
    participant Render as Rendered HTML

    Props->>Component: Pass color prop
    Component->>Component: Create data-attributes
    Component->>Render: Render with data-accent-color
Loading

Possibly related PRs

Suggested reviewers

  • kotAPI

Poem

🐰 A Rabbit's Ode to Colorful Quotes

Blockquotes dancing with hue so bright,
Blue and bold, a colorful delight!
Props that sparkle, attributes that shine,
Code that's crafted with design divine
Hop along, creativity's in flight! 🌈

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 docstrings to generate docstrings for this PR. (Beta)
  • @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.

@kotAPI kotAPI added the automerge A tag that tells kodiak bot to automerge PRs for us when tests and approval conditions are met label Jan 21, 2025
@kodiakhq kodiakhq bot merged commit c8ec466 into rad-ui:main Jan 21, 2025
4 checks passed
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (7)
src/components/ui/BlockQuote/BlockQuote.tsx (3)

12-12: Add JSDoc documentation for the color prop.

Add documentation to describe the purpose and expected values of the color prop.

+/** Accent color for the blockquote. */
 color?: string;

18-22: Follow TypeScript naming conventions.

Use camelCase for variable names instead of snake_case.

-    const data_attributes: Record<string, string> = {};
+    const dataAttributes: Record<string, string> = {};

     if (color) {
-        data_attributes['data-accent-color'] = color;
+        dataAttributes['data-accent-color'] = color;
     }

24-24: Consider validating color values.

The color prop accepts any string value without validation. Consider adding validation or using a union type of allowed colors.

Example implementation:

type AllowedColors = 'blue' | 'green' | 'red' | string;

export type BlockQuoteProps = {
    // ...other props
    /** Accent color for the blockquote. */
    color?: AllowedColors;
}
src/components/ui/BlockQuote/tests/BlockQuote.test.tsx (1)

30-33: Enhance test coverage for the color prop.

Consider adding more test cases to cover:

  • Empty color value
  • Multiple color values
  • Color prop updates

Example additional tests:

test('renders BlockQuote without color when color prop is empty', () => {
    render(<BlockQuote color="">BlockQuote</BlockQuote>);
    expect(screen.getByText('BlockQuote')).not.toHaveAttribute('data-accent-color');
});

test('updates BlockQuote color when prop changes', () => {
    const { rerender } = render(<BlockQuote color="blue">BlockQuote</BlockQuote>);
    expect(screen.getByText('BlockQuote')).toHaveAttribute('data-accent-color', 'blue');
    
    rerender(<BlockQuote color="green">BlockQuote</BlockQuote>);
    expect(screen.getByText('BlockQuote')).toHaveAttribute('data-accent-color', 'green');
});
src/components/ui/BlockQuote/stories/BlockQuote.stories.js (1)

36-40: Enhance color story documentation and examples.

Consider adding:

  • ArgTypes documentation for the color prop
  • Multiple stories showcasing different colors
  • Description of available color options

Example implementation:

export default {
    // ... other config
    argTypes: {
        color: {
            description: 'Accent color for the blockquote',
            control: 'select',
            options: ['blue', 'green', 'red'],
        }
    }
};

export const Colors = {
    render: () => (
        <div className="space-y-4">
            <BlockQuote color="blue">Blue accent</BlockQuote>
            <BlockQuote color="green">Green accent</BlockQuote>
            <BlockQuote color="red">Red accent</BlockQuote>
        </div>
    )
};
docs/app/docs/components/blockquote/page.js (2)

21-23: Enhance color prop documentation.

The current documentation lacks details about:

  • Available color options
  • Usage examples with different colors
  • Best practices for color selection

Example improved documentation:

const data = [
    {
        prop: 'color',
        type: 'string',
        default: 'null',
        description: 'Accent color of the quote. Supports standard color values (e.g., "blue", "green", "red") or custom color values.',
        id: 'color'
    }
];

48-50: Consider adding usage examples section.

Add a section demonstrating different color usage examples to help users understand the available options.

Example implementation:

<Documentation.Section title="Color Examples">
    <div className="space-y-4">
        <BlockQuote color="blue">Blue accent example</BlockQuote>
        <BlockQuote color="green">Green accent example</BlockQuote>
        <BlockQuote color="red">Red accent example</BlockQuote>
    </div>
</Documentation.Section>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 93f9649 and cdf104c.

📒 Files selected for processing (4)
  • docs/app/docs/components/blockquote/page.js (2 hunks)
  • src/components/ui/BlockQuote/BlockQuote.tsx (1 hunks)
  • src/components/ui/BlockQuote/stories/BlockQuote.stories.js (2 hunks)
  • src/components/ui/BlockQuote/tests/BlockQuote.test.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build

customRootClass?: string;
className?: string;
color?:string;
props?: Record<string, any>[]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix props type definition.

The props type should be a generic object, not an array.

-    props?: Record<string, any>[]
+    props?: Record<string, any>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
props?: Record<string, any>[]
props?: Record<string, any>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge A tag that tells kodiak bot to automerge PRs for us when tests and approval conditions are met

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants