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

Added bookmarklink component for headings and link sharing #602

Merged
merged 4 commits into from
Dec 5, 2024

Conversation

impirios
Copy link
Contributor

@impirios impirios commented Dec 4, 2024

closes #475

Have added a BookmarkLink util component for documentation that takes id as a param and it will create a bookmark link out of the children we pass it to.

Summary by CodeRabbit

  • New Features

    • Introduced a new BookMarkLink component for creating bookmark links in the documentation layout.
    • Updated the DocsTable component to wrap headings with BookMarkLink for improved navigation.
  • Bug Fixes

    • Improved import paths for better clarity and maintainability.
  • Style

    • Enhanced readability and formatting of the ComponentFeatures component's JSX.

Copy link
Contributor

coderabbitai bot commented Dec 4, 2024

Warning

Rate limit exceeded

@impirios has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 0 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e973047 and a6b632d.

Walkthrough

The pull request introduces several modifications to the Documentation component and related files. Key changes include updating import paths from relative to absolute, adding a new BookMarkLink component, and wrapping the Heading element within BookMarkLink in the DocsTable and ComponentFeatures components. The overall structure and functionality of the existing components remain unchanged, with no alterations to their logic or error handling.

Changes

File Path Change Summary
docs/components/layout/Documentation/Documentation.js Updated import paths to absolute paths; added import for BookMarkLink; wrapped Heading in BookMarkLink.
docs/components/layout/Documentation/helpers/ComponentFeatures/ComponentFeatures.js Added import for BookMarkLink; wrapped Heading in BookMarkLink; reformatted JSX for clarity.
docs/components/layout/Documentation/utils.js Introduced new BookMarkLink component that creates bookmark links with specified id.

Assessment against linked issues

Objective Addressed Explanation
Add Bookmark link supports for Docs, subheadings (#475)

Possibly related PRs

  • Added text component #452: The changes in this PR involve the addition of the BookMarkLink component, which is also referenced in the main PR, indicating a direct connection in terms of component usage and import statements.

Suggested reviewers

  • kotAPI

🐰 In the garden of code, I hop with glee,
New bookmarks sprout, as fine as can be.
With links to each section, so easy to share,
Documentation's bright, with love and with care!
Hopping through changes, my joy is quite clear,
A world of new links, oh what a great year! 🌼


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 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.

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: 3

🧹 Outside diff range and nitpick comments (2)
docs/components/layout/Documentation/Documentation.js (2)

7-10: Consider using path aliases for imports

The absolute imports are good for maintainability, but consider using path aliases to make them more concise.

Example configuration in your build tool:

// jsconfig.json or tsconfig.json
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@docs/*": ["docs/*"],
      "@components/*": ["components/*"]
    }
  }
}

Then imports could be simplified:

- import CodeBlock from "@/components/layout/Documentation/helpers/CodeBlock"
+ import CodeBlock from "@docs/components/CodeBlock"

Line range hint 1-90: Consider migrating to TypeScript

Given the complexity of the Documentation component and its subcomponents, consider migrating to TypeScript for better type safety and developer experience.

Would you like me to help create a GitHub issue to track this enhancement?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d05ed37 and e973047.

📒 Files selected for processing (3)
  • docs/components/layout/Documentation/Documentation.js (2 hunks)
  • docs/components/layout/Documentation/helpers/ComponentFeatures/ComponentFeatures.js (1 hunks)
  • docs/components/layout/Documentation/utils.js (1 hunks)

Comment on lines 1 to 3
export const BookMarkLink = ({ children, id }) => {
return <div id={id}><a href={`#${id}`}>{children}</a></div>
}
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Enhance accessibility and user experience of BookMarkLink component

The component needs improvements in several areas:

  1. Add ARIA attributes for better screen reader support
  2. Add visual feedback for clickable links
  3. Sanitize the id prop to ensure valid HTML

Consider this enhanced implementation:

- export const BookMarkLink = ({ children, id }) => {
-     return <div id={id}><a href={`#${id}`}>{children}</a></div>
- }
+ export const BookMarkLink = ({ children, id }) => {
+     const sanitizedId = id.toLowerCase().replace(/[^a-z0-9-]/g, '-');
+     return (
+         <div id={sanitizedId}>
+             <a
+                 href={`#${sanitizedId}`}
+                 aria-label={`Direct link to ${id}`}
+                 className="group relative"
+             >
+                 {children}
+                 <span className="ml-2 opacity-0 group-hover:opacity-100 transition-opacity">
+                     #
+                 </span>
+             </a>
+         </div>
+     );
+ }
📝 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
export const BookMarkLink = ({ children, id }) => {
return <div id={id}><a href={`#${id}`}>{children}</a></div>
}
export const BookMarkLink = ({ children, id }) => {
const sanitizedId = id.toLowerCase().replace(/[^a-z0-9-]/g, '-');
return (
<div id={sanitizedId}>
<a
href={`#${sanitizedId}`}
aria-label={`Direct link to ${id}`}
className="group relative"
>
{children}
<span className="ml-2 opacity-0 group-hover:opacity-100 transition-opacity">
#
</span>
</a>
</div>
);
}

Comment on lines +6 to +10
<BookMarkLink id="features">
<Heading as="h6" className="mb-2 text-gray-1000 font-bold">
Features
Features
</Heading>
<div className='mb-10'>
<ul className='list-disc list-inside'>
{
features.map((feature, index) => <li key={index}>{feature}</li>)
}
</ul>
</div>
</BookMarkLink>
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

Avoid hardcoded IDs in BookMarkLink

Using a static "features" ID could cause conflicts if multiple ComponentFeatures components are rendered on the same page.

Consider passing a unique ID based on the component context:

- <BookMarkLink id="features">
+ <BookMarkLink id={`${title?.toLowerCase?.() || 'component'}-features`}>

Also, consider adding PropTypes validation:

import PropTypes from 'prop-types';

ComponentFeatures.propTypes = {
  features: PropTypes.arrayOf(PropTypes.string).isRequired,
  title: PropTypes.string
};

@@ -49,7 +48,7 @@ const DocsTable = ({ children , columns=[], data=[]}) => {


return <div className='mb-20'>
<Heading as="h6" className="mb-4">API Documentation</Heading>
<BookMarkLink id="api-documentation"> <Heading as="h6" className="mb-4">API Documentation</Heading> </BookMarkLink>
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Improve heading hierarchy and accessibility

The current implementation has several concerns:

  1. Using h6 directly might not follow proper document outline
  2. "api-documentation" ID could conflict with multiple instances

Consider this improvement:

- <BookMarkLink id="api-documentation"> 
-   <Heading as="h6" className="mb-4">API Documentation</Heading> 
- </BookMarkLink>
+ <BookMarkLink id={`${title?.toLowerCase?.() || 'component'}-api`}> 
+   <Heading 
+     as={headingLevel || "h2"} 
+     className="mb-4"
+   >
+     API Documentation
+   </Heading> 
+ </BookMarkLink>

Also, consider adding a prop for the heading level to maintain proper document outline:

DocsTable.propTypes = {
  headingLevel: PropTypes.oneOf(['h1', 'h2', 'h3', 'h4', 'h5', 'h6']),
  // ... other props
};

@kotAPI kotAPI merged commit 7539a7f into rad-ui:main Dec 5, 2024
2 checks passed
This was referenced Dec 25, 2024
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.

Add Bookmark link supports for Docs, subheadings
2 participants