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: toc links in the blogs #3562

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

Conversation

r3yc0n1c
Copy link

@r3yc0n1c r3yc0n1c commented Jan 10, 2025

Description

  • Fixed incorrect anchor links (slugs) in the blog's Table of Contents (TOC)

Related issue(s)
Resolves #3540

Demo

bugfix-toc-link.mp4

Summary by CodeRabbit

  • New Features
    • Enhanced table of contents (TOC) navigation with improved scroll identification and linking
    • Updated TOC item identifiers for more precise document navigation

Copy link

coderabbitai bot commented Jan 10, 2025

Walkthrough

The changes in the TOC.tsx component modify how table of contents (TOC) items are processed and rendered. The key modification involves introducing a new slugWithATag property to replace the previous slug property. This change impacts how TOC items are mapped for the Scrollspy component and how href attributes are generated for anchor elements, potentially addressing navigation and linking issues within the blog's table of contents.

Changes

File Change Summary
components/TOC.tsx - Added slugWithATag property to TOC items
- Updated Scrollspy items mapping
- Modified href attribute generation for TOC links

Assessment against linked issues

Objective Addressed Explanation
TOC links not working [#3540]
Smooth scrolling to sections Requires additional verification of scroll behavior

Poem

🐰 A rabbit's tale of links so bright,
Slugs transformed with coding might!
TOC now dances, smooth and clean,
No more broken links to be seen
Hop along the page with glee! 🌟


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.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link

codecov bot commented Jan 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (67b292a) to head (175484c).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3562   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           19        19           
  Lines          668       668           
=========================================
  Hits           668       668           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

netlify bot commented Jan 10, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 175484c
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67819c0be61d9c0008d0a539
😎 Deploy Preview https://deploy-preview-3562--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@r3yc0n1c r3yc0n1c changed the title fix: TOC links in the blogs fix: toc links in the blogs Jan 10, 2025
Copy link

@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

🔭 Outside diff range comments (1)
components/TOC.tsx (1)

Line range hint 8-14: Add slugWithATag to the interface definition.

The interface ITOCProps needs to be updated to include the new slugWithATag property that's being used in the implementation. This will ensure type safety and prevent potential runtime errors.

Apply this diff to fix the interface:

 interface ITOCProps {
   className?: string;
   cssBreakingPoint?: string;
   toc: {
     lvl: number;
     content: string;
     slug: string;
+    slugWithATag?: string;
   }[];
   contentSelector?: string;
   depth?: number;
 }
🧹 Nitpick comments (1)
components/TOC.tsx (1)

Line range hint 34-39: Enhance slug transformation for better compatibility.

The current slug transformation could be improved to handle:

  1. Consecutive special characters that might result in multiple hyphens
  2. Non-ASCII characters that could cause inconsistent slugs
  3. Edge cases with special characters

Consider using a robust slugification library or apply this enhanced transformation:

       slugWithATag: item.content
-        .replace(/[<>?!:`'."\\/=]/gi, '')
-        .replace(/\s/gi, '-')
-        .toLowerCase()
+        .toLowerCase()
+        .normalize('NFD')
+        .replace(/[\u0300-\u036f]/g, '')  // Remove diacritics
+        .replace(/[^a-z0-9\s-]/g, '')     // Remove special chars
+        .trim()
+        .replace(/[\s-]+/g, '-')          // Replace spaces and repeated hyphens
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 67b292a and 175484c.

📒 Files selected for processing (1)
  • components/TOC.tsx (2 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (4)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
components/TOC.tsx (1)

Line range hint 78-91: Verify unique slugs to prevent scroll spy issues.

While the changes to use slugWithATag are correct, there's no validation to ensure unique slugs. Duplicate slugs could cause the scroll spy to behave incorrectly when multiple headings transform to the same slug.

Consider adding a uniqueness check or suffix for duplicate slugs:

       slugWithATag: item.content
         .replace(/[<>?!:`'."\\/=]/gi, '')
         .replace(/\s/gi, '-')
-        .toLowerCase()
+        .toLowerCase(),
+      // Add a suffix for duplicate slugs
+      slugWithATag: (slugs => {
+        let base = /* ... existing transformation ... */;
+        let unique = base;
+        let counter = 1;
+        while (slugs.includes(unique)) {
+          unique = `${base}-${counter++}`;
+        }
+        slugs.push(unique);
+        return unique;
+      })([])

Run this script to check for duplicate slugs in the existing content:

@asyncapi-bot
Copy link
Contributor

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 40
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-3562--asyncapi-website.netlify.app/

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.

[BUG] Blog Table of contents links not working
2 participants