Skip to content
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(docs): incorrect code in Modal placement #4652

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

wingkwong
Copy link
Member

@wingkwong wingkwong commented Jan 26, 2025

Closes #4649

📝 Description

⛳️ Current behavior (updates)

🚀 New behavior

💣 Is this a breaking change (Yes/No):

📝 Additional Information

Summary by CodeRabbit

  • New Features

    • Enhanced modal placement options with new configuration settings
    • Added support for multiple modal positioning modes including auto, top, bottom, center, top-center, and bottom-center
  • Documentation

    • Updated user interface labels to reflect new modal placement functionality
    • Simplified modal content presentation

@wingkwong wingkwong added the 📋 Scope : Docs Related to the documentation label Jan 26, 2025
Copy link

linear bot commented Jan 26, 2025

Copy link

changeset-bot bot commented Jan 26, 2025

⚠️ No Changeset found

Latest commit: 00bdd04

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Jan 26, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
heroui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 26, 2025 5:46am
heroui-sb ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 26, 2025 5:46am

Copy link
Contributor

coderabbitai bot commented Jan 26, 2025

Walkthrough

The changes involve modifying the modal component documentation to introduce a new feature for modal placement. The implementation replaces the previous scroll behavior state with a new modalPlacement state, providing more flexible positioning options for modals. The documentation now includes options like "auto," "top," "bottom," "center," "top-center," and "bottom-center" for modal placement, updating the component's props and user interface accordingly.

Changes

File Change Summary
apps/docs/content/components/modal/placement.raw.jsx - Added modalPlacement state variable
- Updated useState import from React
- Modified RadioGroup label and options
- Changed modal prop from scrollBehavior to placement
- Removed excess paragraphs in ModalBody

Sequence Diagram

sequenceDiagram
    participant User
    participant Component
    participant Modal
    User->>Component: Select modal placement
    Component->>Modal: Set placement prop
    Modal->>User: Render modal at specified position
Loading

Assessment against linked issues

Objective Addressed Explanation
Modal placement example
Remove code overflow scroll
Provide modal placement code
✨ 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.

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.

@wingkwong wingkwong changed the title fix(docs): incorrect code Modal placement fix(docs): incorrect code in Modal placement Jan 26, 2025
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: 0

🧹 Nitpick comments (3)
apps/docs/content/components/modal/placement.raw.jsx (3)

1-1: Consider using constants for placement values.

Define placement options as constants to maintain consistency and prevent typos throughout the code.

+const MODAL_PLACEMENTS = {
+  AUTO: "auto",
+  TOP: "top",
+  BOTTOM: "bottom",
+  CENTER: "center",
+  TOP_CENTER: "top-center",
+  BOTTOM_CENTER: "bottom-center",
+} as const;

-const [modalPlacement, setModalPlacement] = useState("auto");
+const [modalPlacement, setModalPlacement] = useState(MODAL_PLACEMENTS.AUTO);

Also applies to: 16-16


23-34: Enhance accessibility for the RadioGroup component.

Consider adding an aria-label to improve screen reader experience.

 <RadioGroup
   label="Select modal placement"
+  aria-label="Modal placement options"
   orientation="horizontal"
   value={modalPlacement}
   onValueChange={setModalPlacement}
 >

36-36: Add JSDoc comment to document placement options.

Consider adding a comment to document the available placement options for better developer experience.

+/**
+ * Modal component with configurable placement
+ * @param {string} placement - One of: "auto", "top", "bottom", "center", "top-center", "bottom-center"
+ */
 <Modal isOpen={isOpen} placement={modalPlacement} onOpenChange={onOpenChange}>
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ceb6385 and 00bdd04.

📒 Files selected for processing (1)
  • apps/docs/content/components/modal/placement.raw.jsx (2 hunks)
🔇 Additional comments (2)
apps/docs/content/components/modal/placement.raw.jsx (2)

19-22: Clean and well-structured layout implementation!

The flex layout with proper spacing and centered alignment provides a good user experience for the demo.


36-36: Verify Modal component prop types support.

Let's verify that the Modal component properly supports all the new placement values.

✅ Verification successful

✅ Modal placement prop is properly supported

The Modal component fully supports the placement prop with the following valid values: auto (default), center, top, top-center, bottom, and bottom-center. The implementation includes proper TypeScript types and corresponding layout styles.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for Modal component prop types definition
ast-grep --pattern 'interface ModalProps {
  $$$
  placement?: $_
  $$$
}'

Length of output: 76


Script:

#!/bin/bash
# Search for Modal component and placement prop definitions using multiple patterns
echo "=== Searching for Modal component definition ==="
rg -A 10 "export.*Modal.*=" 

echo "=== Searching for placement prop usage ==="
rg "placement.*=.*{" --type ts --type tsx --type jsx

echo "=== Searching for type definitions ==="
ast-grep --pattern 'type ModalProps = {
  $$$
}'

Length of output: 3129


Script:

#!/bin/bash
# Search for Modal implementation and placement prop
echo "=== Searching for Modal props and placement in core files ==="
rg -A 5 "type.*Modal.*Props" packages/components/modal/src/
rg -A 5 "interface.*Modal.*Props" packages/components/modal/src/

echo "=== Searching for placement in modal variants ==="
cat packages/core/theme/src/components/modal.ts

echo "=== Searching for placement prop usage with fixed pattern ==="
rg "placement.*=" --type ts --type tsx --type jsx

Length of output: 9574

@wingkwong wingkwong linked an issue Jan 26, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📋 Scope : Docs Related to the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Model placement of modal popup
2 participants