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

docs(generator): update latest generator documentation #3573

Conversation

asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Jan 14, 2025

Updated generator documentation is available and this PR introduces update to generator folder on the website

Summary by CodeRabbit

  • Documentation
    • Updated API documentation for the Generator class
    • Deprecated generateFromString method
    • Updated return types for generateFromString, generateFromURL, and generateFromFile methods
    • Clarified GitHub Actions documentation for AsyncAPI document generation

Copy link

coderabbitai bot commented Jan 14, 2025

Walkthrough

The pull request introduces documentation updates for the AsyncAPI Generator library. The changes primarily focus on the API documentation for the Generator class, including method deprecation and return type modifications. Specifically, the generateFromString method is marked as deprecated, and the return types for generateFromString, generateFromURL, and generateFromFile methods are updated to Promise.<(TemplateRenderResult|undefined)>. Additionally, a note in the installation guide is refined to clarify the context of GitHub Actions for AsyncAPI documents.

Changes

File Change Summary
markdown/docs/tools/generator/api.md - Deprecated generateFromString method
- Updated return types for generateFromString, generateFromURL, and generateFromFile methods to `Promise.<(TemplateRenderResult
markdown/docs/tools/generator/installation-guide.md - Updated note about GitHub Actions to specify "Github Actions for Generator for AsyncAPI documents"

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • magicmatatjahu
  • devilkiller-ag
  • akshatnema
  • sambhavgupta0705
  • anshgoyalevil
  • Mayaleeeee
  • asyncapi-bot-eve

Poem

🐰 Docs dancing with grace,
Methods evolving, finding their place
Deprecated paths gently fade
New types and clarity are made
AsyncAPI's story, ever bright! 📝✨


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

netlify bot commented Jan 14, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit e99a5ce
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67861980eca9ca00087b04f4
😎 Deploy Preview https://deploy-preview-3573--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.

Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (e3722be) to head (e99a5ce).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3573   +/-   ##
=========================================
  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.

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

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

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

@asyncapi-bot asyncapi-bot merged commit 78c6f2d into master Jan 14, 2025
33 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-generator-docs-7fe7bbb8c97da69b7e3a42e39a724b1022ebf5ae branch January 14, 2025 08:03
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: 1

🧹 Nitpick comments (2)
markdown/docs/tools/generator/api.md (2)

42-42: Add migration guidance for deprecated method.

The deprecation notice for generateFromString should include information about the recommended alternative method that developers should use instead.

Consider adding a note like this:

- ~~[.generateFromString(asyncapiString, [parseOptions])](#Generator+generateFromString) ⇒ `Promise.<(TemplateRenderResult|undefined)>`~~
+ ~~[.generateFromString(asyncapiString, [parseOptions])](#Generator+generateFromString) ⇒ `Promise.<(TemplateRenderResult|undefined)>`~~ **Deprecated:** Use `generate(asyncapiString, parseOptions)` instead.
🧰 Tools
🪛 Markdownlint (0.37.0)

42-42: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


42-44: Fix markdown list indentation.

The unordered list items are indented with 8 spaces, but markdown style guide recommends 4 spaces.

Apply this formatting change:

-        * ~~[.generateFromString(asyncapiString, [parseOptions])](#Generator+generateFromString) ⇒ `Promise.<(TemplateRenderResult|undefined)>`~~
-        * [.generateFromURL(asyncapiURL)](#Generator+generateFromURL) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
-        * [.generateFromFile(asyncapiFile)](#Generator+generateFromFile) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
+    * ~~[.generateFromString(asyncapiString, [parseOptions])](#Generator+generateFromString) ⇒ `Promise.<(TemplateRenderResult|undefined)>`~~
+    * [.generateFromURL(asyncapiURL)](#Generator+generateFromURL) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
+    * [.generateFromFile(asyncapiFile)](#Generator+generateFromFile) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
🧰 Tools
🪛 Markdownlint (0.37.0)

42-42: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


43-43: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


44-44: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e3722be and e99a5ce.

📒 Files selected for processing (2)
  • markdown/docs/tools/generator/api.md (1 hunks)
  • markdown/docs/tools/generator/installation-guide.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • markdown/docs/tools/generator/installation-guide.md
🧰 Additional context used
🪛 Markdownlint (0.37.0)
markdown/docs/tools/generator/api.md

42-42: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


43-43: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


44-44: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)

⏰ Context from checks skipped due to timeout of 180000ms (2)
  • GitHub Check: Automerge PR autoapproved by a bot
  • GitHub Check: Lighthouse CI

Comment on lines +43 to +44
* [.generateFromURL(asyncapiURL)](#Generator+generateFromURL) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
* [.generateFromFile(asyncapiFile)](#Generator+generateFromFile) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Document cases where methods return undefined.

The return types for generateFromURL and generateFromFile now include undefined as a possible return value, but there's no documentation explaining under what conditions this occurs.

Consider adding documentation like this:

- [.generateFromURL(asyncapiURL)](#Generator+generateFromURL) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
+ [.generateFromURL(asyncapiURL)](#Generator+generateFromURL) ⇒ `Promise.<(TemplateRenderResult|undefined)>` - Returns undefined when [specify condition]

- [.generateFromFile(asyncapiFile)](#Generator+generateFromFile) ⇒ `Promise.<(TemplateRenderResult|undefined)>`
+ [.generateFromFile(asyncapiFile)](#Generator+generateFromFile) ⇒ `Promise.<(TemplateRenderResult|undefined)>` - Returns undefined when [specify condition]

Committable suggestion skipped: line range outside the PR's diff.

🧰 Tools
🪛 Markdownlint (0.37.0)

43-43: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)


44-44: Expected: 4; Actual: 8
Unordered list indentation

(MD007, ul-indent)

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.

2 participants