Skip to content

docs: removing --use-new-generator flag refference#5065

Open
Jatin24062005 wants to merge 1 commit intoasyncapi:masterfrom
Jatin24062005:Fixing_Inconsistency_due_Removed_--use-new-generator
Open

docs: removing --use-new-generator flag refference#5065
Jatin24062005 wants to merge 1 commit intoasyncapi:masterfrom
Jatin24062005:Fixing_Inconsistency_due_Removed_--use-new-generator

Conversation

@Jatin24062005
Copy link

@Jatin24062005 Jatin24062005 commented Feb 2, 2026

Description
This PR removes outdated references to the --use-new-generator flag from the project website. The flag was deprecated and removed from the CLI, but the website still mentioned it. This update ensures consistency between the website and the Generator Library documentation.

Related issue(s)
asyncapi/generator#1872

Summary by CodeRabbit

  • Documentation

    • Updated CLI usage examples across generator documentation to reflect current command behavior.
    • Revised template generation guidance with concrete versioning examples and improved formatting.
  • Bug Fixes

    • Simplified default generator installation parameters for improved consistency.

@netlify
Copy link

netlify bot commented Feb 2, 2026

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 7cf5f39
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/698082bb11d4f30008871216
😎 Deploy Preview https://deploy-preview-5065--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.

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.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 2, 2026

📝 Walkthrough

Walkthrough

The changes remove the --use-new-generator flag from CLI generator documentation and component defaults, simplifying command-line examples and reducing default parameters passed to the generator tool.

Changes

Cohort / File(s) Summary
Generator Documentation
markdown/docs/tools/generator/usage.md, markdown/docs/tools/generator/versioning.md
Removed --use-new-generator flag from CLI examples; reformatted documentation note to blockquote style; replaced generic example with concrete versioned package versions.
Component Defaults
components/GeneratorInstallation.tsx
Changed default command-line parameters from -o example --use-new-generator to -o example .

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A flag once danced through every command line,
But now it bids farewell, a simpler design,
No more --use-new-generator in the way,
Documentation cleaner for a brighter day,
With -o example fresh and light,
Our generator docs shine ever bright! ✨

🚥 Pre-merge checks | ✅ 3
✅ 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 accurately describes the main change: removing references to the --use-new-generator flag from the codebase.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 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.

@codecov
Copy link

codecov bot commented Feb 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (229d0b9) to head (7cf5f39).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5065   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          796       796           
  Branches       146       146           
=========================================
  Hits           796       796           

☔ 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

⚡️ Lighthouse report for the changes in this PR:

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

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
markdown/docs/tools/generator/versioning.md (1)

18-31: ⚠️ Potential issue | 🟡 Minor

Update pinned versions to current releases and add context for legacy examples.

The versions @asyncapi/cli@0.20.0 and @asyncapi/html-template@0.7.0 do exist on npm and are not officially deprecated, but they are 4–6 years old (from June 2022 and May 2020 respectively). Current safe releases are @asyncapi/cli@5.0.7+ or @asyncapi/cli@6.0.0 (released Feb 1, 2026) and @asyncapi/html-template@3.5.4.

The second code example mixes an old generator workflow without explanation. Either update both examples to current versions or clearly mark the second example as legacy/compatibility-testing documentation.

🤖 Fix all issues with AI agents
In `@markdown/docs/tools/generator/usage.md`:
- Around line 60-61: The inline code span shown in the template usage contains
an extra leading space (" {{ params.title }}") which violates MD038; edit the
markdown so the inline code has no inner spaces—change the snippet to use `{{
params.title }}` (remove the leading/trailing space inside the code span)
wherever the template example appears to satisfy the lint rule.
🧹 Nitpick comments (1)
components/GeneratorInstallation.tsx (1)

24-27: Remove the trailing space in the default params string.

This space is interpolated into generated npm and Docker commands (lines 57 and 65), resulting in trailing whitespace in command examples shown to users.

♻️ Proposed fix
-  const [params, setParams] = useState<string>('-o example ');
+  const [params, setParams] = useState<string>('-o example');

Comment on lines 60 to 61

In the template you can use it like this: ` {{ params.title }}`
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 | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

# First, check if the file exists and read lines around 60-61
wc -l markdown/docs/tools/generator/usage.md

Repository: asyncapi/website

Length of output: 102


🏁 Script executed:

# Read the relevant section of the file with context
sed -n '55,65p' markdown/docs/tools/generator/usage.md | cat -n

Repository: asyncapi/website

Length of output: 529


🏁 Script executed:

# Run markdownlint to check for violations in this file
npx markdownlint-cli2 markdown/docs/tools/generator/usage.md 2>&1

Repository: asyncapi/website

Length of output: 4885


🏁 Script executed:

# Create a test version with the proposed fix and verify it resolves MD038
sed '61s/` {{ params.title }}`/`{{ params.title }}`/' markdown/docs/tools/generator/usage.md > /tmp/usage_fixed.md

# Run markdownlint on the fixed version and filter for MD038 on line 61
npx markdownlint-cli2 /tmp/usage_fixed.md 2>&1 | grep -E "61.*MD038" || echo "No MD038 error on line 61 after fix"

Repository: asyncapi/website

Length of output: 95


Remove inner space in inline code to satisfy MD038.

Line 61 has spaces inside a code span, which violates the MD038 linting rule. Remove the leading space to fix.

✏️ Proposed fix
-In the template you can use it like this: ` {{ params.title }}`
+In the template you can use it like this: `{{ params.title }}`
📝 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
In the template you can use it like this: ` {{ params.title }}`
In the template you can use it like this: `{{ params.title }}`
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)

[warning] 61-61: Spaces inside code span elements

(MD038, no-space-in-code)

🤖 Prompt for AI Agents
In `@markdown/docs/tools/generator/usage.md` around lines 60 - 61, The inline code
span shown in the template usage contains an extra leading space (" {{
params.title }}") which violates MD038; edit the markdown so the inline code has
no inner spaces—change the snippet to use `{{ params.title }}` (remove the
leading/trailing space inside the code span) wherever the template example
appears to satisfy the lint rule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To Be Triaged

Development

Successfully merging this pull request may close these issues.

2 participants

Comments