Skip to content

Conversation

@hk2166
Copy link

@hk2166 hk2166 commented Nov 7, 2025

Removed the Glee framework installation docs from the "Getting Started" docs
Issue #4559

Summary by CodeRabbit

Documentation

  • Updated code generation tutorial to focus on AsyncAPI Generator
  • Revised prerequisites and installation instructions
  • Added new template options and custom templates sections
  • Updated usage examples and available templates reference
  • Removed project-specific examples for broader applicability

@netlify
Copy link

netlify bot commented Nov 7, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 7627f0e
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/690e3026755ed60008703233
😎 Deploy Preview https://deploy-preview-4560--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.

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Nov 7, 2025

We require all PRs to follow Conventional Commits specification.
More details 👇🏼

 No release type found in pull request title "fixed the archived/deprecated Glee framework #4559". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 7, 2025

Walkthrough

The tutorial content is completely rewritten to guide users through code generation using the AsyncAPI Generator tool instead of the Glee framework. Prerequisites, installation steps, commands, templates, and examples are updated to reflect the official generator's approach and ecosystem.

Changes

Cohort / File(s) Summary
Tutorial rewrite
markdown/docs/tutorials/generate-code.md
Complete restructuring from Glee-centric to AsyncAPI Generator-centric tutorial. Introduction, prerequisites, and installation steps updated to use Node.js and official generator. Command examples replaced with ag syntax. "Available Templates" section expanded with official templates and repository references. New "Template Options" subsection added. Replaces project-specific steps with "Custom Templates" and "Next Steps" sections.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Entire tutorial has been restructured with substantial content rewrite across multiple sections
  • Verify that all AsyncAPI Generator command syntax and template references are accurate and current
  • Confirm that prerequisites (Node.js, npm, global installation) are correct and complete
  • Review template examples and template repository references for correctness
  • Ensure no outdated Glee or CLI references remain unintentionally

Possibly related PRs

  • #3479: Modifies the same tutorial file with overlapping command/template usage examples.

Suggested reviewers

  • quetzalliwrites
  • TRohit20
  • thulieblack
  • VaishnaviNandakumar
  • asyncapi-bot-eve

Poem

🐰 A generator tale we now tell,
From Glee to AsyncAPI's spell,
Templates guide the way,
Code blooms from the fray,
This tutorial's magic works well! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title describes updating documentation from a deprecated framework to a supported alternative, which is the primary change in the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • 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

Comment @coderabbitai help to get the list of available commands and usage tips.

@asyncapi-bot
Copy link
Contributor

⚡️ Lighthouse report for the changes in this PR:

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

Lighthouse ran on https://deploy-preview-4560--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: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 445e7c1 and 7627f0e.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • markdown/docs/tutorials/generate-code.md (1 hunks)
⏰ 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). (1)
  • GitHub Check: Lighthouse CI
🔇 Additional comments (8)
markdown/docs/tutorials/generate-code.md (8)

2-5: Frontmatter looks good.

The metadata is clear and well-suited for documentation navigation.


7-9: Clear and focused introduction.

The heading and opening sentence effectively communicate the tutorial's purpose.


11-15: Verify version requirements and clarify the AsyncAPI document prerequisite.

The specific Node.js and npm version numbers should be confirmed as accurate minimum requirements. Additionally, "An AsyncAPI document" is vague—consider linking to example documents or documentation that explains what constitutes a valid AsyncAPI document for users unfamiliar with the specification.


17-23: Installation instructions are clear and correct.

The npm install command is properly formatted and the global installation approach is appropriate for a getting-started tutorial.


25-37: Basic usage section is well-structured and provides a concrete example.

The command syntax and example are clear. Users should be able to run the HTML template example without issue.


39-49: Template section provides good overview with link to complete repository.

The selection of templates shown is representative, and the link to the template repository appropriately directs users to the authoritative source for all available options.


51-63: Template Options section effectively teaches discovery of template configuration.

The ag help <template> command is a practical way for users to learn about template-specific options without needing to consult external documentation first.


65-73: Next Steps section provides good progression paths.

The references to further documentation, template development guide, and community are appropriate for continuing users' learning journey.

Comment on lines +11 to +15
## Prerequisites

Glee is often used with the [AsyncAPI CLI](/tools/cli) for a better development experience.
- Node.js v20.12.0 or later
- npm v10.5.0 or later
- An AsyncAPI document
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 | 🔴 Critical

🧩 Analysis chain

Verify external links and Node.js/npm version requirements.

This tutorial references several external URLs and specific software versions that should be validated:

External Links to verify:

  • Line 49: GitHub AsyncAPI Generator templates link
  • Line 67, 72: Template Development Guide link
  • Line 71: Main AsyncAPI Generator documentation link
  • Line 73: AsyncAPI Community link

Version Requirements to verify:

  • Line 13-14: Node.js v20.12.0 and npm v10.5.0—confirm these are accurate minimum versions (not overly restrictive) and match current @asyncapi/generator requirements

All links should be tested for validity and confirmed to lead to active, relevant documentation. Version numbers should be cross-referenced with the package's package.json or official documentation to ensure they reflect current requirements.

Also applies to: 39-49, 65-73


🏁 Script executed:

#!/bin/bash
# Description: Verify external links are reachable and check AsyncAPI Generator package requirements

# Check HTTP status of all external links
echo "=== Checking external links ==="
curl -s -o /dev/null -w "GitHub templates: %{http_code}\n" https://github.com/asyncapi/generator#templates
curl -s -o /dev/null -w "Template dev guide: %{http_code}\n" https://www.asyncapi.com/docs/tools/generator/template-development
curl -s -o /dev/null -w "Generator docs: %{http_code}\n" https://www.asyncapi.com/docs/tools/generator
curl -s -o /dev/null -w "Community: %{http_code}\n" https://www.asyncapi.com/community

# Check current version requirements from npm package
echo -e "\n=== AsyncAPI Generator package requirements ==="
npm view @asyncapi/generator engines --json 2>/dev/null || echo "Could not fetch package info"

# Check if package exists and get latest version
echo -e "\n=== Latest package info ==="
npm view @asyncapi/generator version 2>/dev/null || echo "Could not fetch version info"

Length of output: 243


Update version requirements to match package minimums or clarify tested compatibility.

All external links validate successfully (HTTP 200). However, the tutorial specifies overly restrictive version requirements:

Current tutorial requirements:

  • Node.js v20.12.0 or later
  • npm v10.5.0 or later

Actual @asyncapi/generator requirements:

  • Node.js >=18.12.0
  • npm >=8.19.0

The tutorial versions are 2+ major versions higher than the package's documented minimum requirements. Consider either:

  1. Updating to the package minimums (v18.12.0 and v8.19.0) for broader compatibility, or
  2. If v20.12.0/v10.5.0 represent tested/recommended versions, clarify this in the tutorial text (e.g., "tested with" vs. "required")
🤖 Prompt for AI Agents
In markdown/docs/tutorials/generate-code.md around lines 11-15, the Node.js and
npm version requirements are stricter than the package's documented minimums;
update the listed versions to the actual @asyncapi/generator minimums (Node.js
>=18.12.0 and npm >=8.19.0) OR, if those higher versions (Node.js v20.12.0 and
npm v10.5.0) are intended as tested/recommended rather than required, change the
wording to clarify this (e.g., "Tested with Node.js v20.12.0 and npm v10.5.0;
minimum requirements: Node.js >=18.12.0, npm >=8.19.0").

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.

2 participants