Skip to content

Conversation

@bandantonio
Copy link
Collaborator

@bandantonio bandantonio commented Aug 20, 2025

Description

Fix for the broken reference links that appear as empty bullet points on the AsyncAPI document structure page

Before After
Screenshot 2025-08-20 at 3 24 37 AM Screenshot 2025-08-20 at 3 22 55 AM

Related issue(s)
Fixes #4307

Summary by CodeRabbit

  • Documentation
    • Reformatted the reference link list in the AsyncAPI document structure guide for consistency and readability.
    • Updated list markers only; link texts, targets, and anchors remain unchanged.
    • No content, semantics, or feature behavior affected.

@netlify
Copy link

netlify bot commented Aug 20, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit a5b599a
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/68b6e39c8b1f350008bba66e
😎 Deploy Preview https://deploy-preview-4337--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 project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 20, 2025

Walkthrough

Formatting-only edits to a single docs page: the bullet list of reference links in markdown/docs/concepts/asyncapi-document/structure.md switches from "-" to "+" markers. No content, links, or semantics changed.

Changes

Cohort / File(s) Summary
Docs formatting
markdown/docs/concepts/asyncapi-document/structure.md
Converted list bullet markers from "-" to "+" for a reference link block; no textual or URL changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective Addressed Explanation
Fix strange bottom bullet list on /docs/concepts/asyncapi-document/structure (#4307) Only bullet marker style changed; list structure/visibility not adjusted.

Possibly related PRs

Suggested labels

ready-to-merge, 📑 docs, area/docs

Suggested reviewers

  • thulieblack
  • asyncapi-bot-eve
  • TRohit20
  • sambhavgupta0705

Poem

I nibbled at bullets, a tidy delight,
Swapped dashes for pluses, neat as midnight.
No links were munched, no text astray—
Just grooming the grass where docs display.
Hop hop! The list now sits just right. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@codecov
Copy link

codecov bot commented Aug 20, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (250823b) to head (a5b599a).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4337   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Aug 20, 2025

⚡️ Lighthouse report for the changes in this PR:

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

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

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 (1)
markdown/docs/concepts/asyncapi-document/structure.md (1)

425-447: Optional: consider pinning to a stable spec version instead of “latest”.

Linking to “latest” can break anchors in the future if headings/IDs change. If the website supports stable version aliases (for example, v3 or a specific version), consider pinning these references to reduce maintenance churn. If you prefer “latest” for freshness, keep as-is.

If you confirm the preferred version alias, I can provide a one-shot diff to update all definitions consistently.

📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between dbcd681 and 00e3c76.

📒 Files selected for processing (1)
  • markdown/docs/concepts/asyncapi-document/structure.md (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-19T20:58:34.040Z
Learnt from: bandantonio
PR: asyncapi/website#4264
File: markdown/docs/tutorials/getting-started/coming-from-openapi.md:24-25
Timestamp: 2025-07-19T20:58:34.040Z
Learning: In the AsyncAPI website documentation, anchor references to specification sections can use camelCase format (e.g., #serverObject, #parameterObject, #messageObject) even if the actual HTML IDs on the spec page use hyphenated lowercase format. This is acceptable and should not be changed.

Applied to files:

  • markdown/docs/concepts/asyncapi-document/structure.md
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Lighthouse CI
🔇 Additional comments (2)
markdown/docs/concepts/asyncapi-document/structure.md (2)

425-448: Good fix: adding explicit reference definitions removes empty bullets and restores links.

Defining all link reference labels at the bottom is the right way to resolve the stray empty bullet list reported in #4307. The label names match their usages throughout the doc, and the targets consistently point to the spec “latest” page.


431-431: Keep as-is — the spec exposes #operationObject (no #operationItemObject).

I checked https://www.asyncapi.com/docs/reference/specification/latest — the page contains id="operationObject" and no id="operationItemObject", so the current link is correct.

  • File: markdown/docs/concepts/asyncapi-document/structure.md — line ~431
    • Keep: [operation-item-object]: /docs/reference/specification/latest#operationObject

Likely an incorrect or invalid review comment.

@thulieblack
Copy link
Member

/rtm

@asyncapi-bot asyncapi-bot merged commit 039f99f into asyncapi:master Sep 2, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feedback on /docs/concepts/asyncapi-document/structure - Mon, 04 Aug 2025 00:14:32 GMT

3 participants