Skip to content

Conversation

varshitha-besthu
Copy link

Description

Summary

This PR adds a note about baked-in templates (experimental) in the main README.md under the List of official generator templates section.

Why

  • The README is the most frequently visited entry point for users and contributors.
  • Adding this note helps people understand what baked-in templates are and where to find them.
  • Provides visibility into ongoing experimental work.

Changes

  • Added an [!IMPORTANT] note with a link to the baked-in templates documentation.

Related issue(s)
Resolves #1718

Copy link

changeset-bot bot commented Sep 18, 2025

⚠️ No Changeset found

Latest commit: cb0113c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@asyncapi-bot
Copy link
Contributor

What reviewer looks at during PR review

The following are ideal points maintainers look for during review. Reviewing these points yourself beforehand can help streamline the review process and reduce time to merge.

  1. PR Title: Use a concise title that follows our Conventional Commits guidelines and clearly summarizes the change using imperative mood (it means spoken or written as if giving a command or instruction, like "add new helper for listing operations")

    Note - In Generator, prepend feat: or fix: in PR title only when PATCH/MINOR release must be triggered.

  2. PR Description: Clearly explain the issue being solved, summarize the changes made, and mention the related issue.

    Note - In Generator, we use Maintainers Work board to track progress. Ensure the PR Description includes Resolves #<issue-number> or Fixes #<issue-number> this will automatically close the linked issue when the PR is merged and helps automate the maintainers workflow.

  3. Documentation: Update the relevant Generator documentation to accurately reflect the changes introduced in the PR, ensuring users and contributors have up-to-date guidance.

  4. Comments and JSDoc: Write clear and consistent JSDoc comments for functions, including parameter types, return values, and error conditions, so others can easily understand and use the code.

  5. DRY Code: Ensure the code follows the Don't Repeat Yourself principle. Look out for duplicate logic that can be reused.

  6. Test Coverage: Ensure the new code is well-tested with meaningful test cases that pass consistently and cover all relevant edge cases.

  7. Commit History: Contributors should avoid force-pushing as much as possible. It makes it harder to track incremental changes and review the latest updates.

  8. Template Design Principles Alignment: While reviewing template-related changes in the packages/ directory, ensure they align with the Assumptions and Principles. If any principle feels outdated or no longer applicable, start a discussion these principles are meant to evolve with the project.

  9. Reduce Scope When Needed: If an issue or PR feels too large or complex, consider splitting it and creating follow-up issues. Smaller, focused PRs are easier to review and merge.

  10. Bot Comments: As reviewers, check that contributors have appropriately addressed comments or suggestions made by automated bots. If there are bot comments the reviewer disagrees with, react to them or mark them as resolved, so the review history remains clear and accurate.

Copy link
Contributor

@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
Member

@Adi-204 Adi-204 left a comment

Choose a reason for hiding this comment

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

@varshitha-besthu I think we should write about what exactly Baked-in Templates,

Below is just suggestion feel free to change it -

Baked-in templates are official AsyncAPI templates shipped with the Generator (@asyncapi/generator). They cover code, docs, configs, and SDKs, and are maintained under packages/templates with a consistent, opinionated structure for reliability and ease of maintenance. It is not recommended to use them in production. 

I would suggest you to read - https://www.asyncapi.com/docs/tools/generator/baked-in-templates

Also you need to add same in https://github.com/asyncapi/generator/tree/master/apps/generator#readme

Copy link

Copy link
Member

@Adi-204 Adi-204 left a comment

Choose a reason for hiding this comment

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

@varshitha-besthu left few comments! do same changes in app/generator/README.md


You can find above templates and the ones provided by the community in **[this list](https://github.com/search?q=topic%3Aasyncapi+topic%3Agenerator+topic%3Atemplate)**

[!IMPORTANT]
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
[!IMPORTANT]
> [!IMPORTANT]

Comment on lines +74 to +75


Copy link
Member

Choose a reason for hiding this comment

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

Suggested change

**Note on Baked-in Templates**

AsyncAPI Generator also comes with **baked-in templates** - official templates shipped directly inside the Generator (`@asyncapi/generator`).
They include code, documentation, config, and SDK templates, all maintained under the [`/packages/templates`](./packages/templates) folder with a strict, opinionated structure.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
They include code, documentation, config, and SDK templates, all maintained under the [`/packages/templates`](./packages/templates) folder with a strict, opinionated structure.
They include code, documentation, config, and SDK templates, all maintained under the [`/packages/templates`](packages/templates) folder with a strict, opinionated structure.


AsyncAPI Generator also comes with **baked-in templates** - official templates shipped directly inside the Generator (`@asyncapi/generator`).
They include code, documentation, config, and SDK templates, all maintained under the [`/packages/templates`](./packages/templates) folder with a strict, opinionated structure.

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change

Comment on lines +70 to +71
⚠️ This feature is experimental and not recommended for production use.
Instead, we encourage you to try them out and share feedback or contribute with your use cases.
Copy link
Member

Choose a reason for hiding this comment

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

Just keep them in same line no need of new line for new sentence.

@derberg derberg moved this to In Progress in Maintainers work Sep 24, 2025
@Adi-204
Copy link
Member

Adi-204 commented Sep 30, 2025

I believe this PR should be closed as it is currently blocking others from contributing. The PR was reviewed 7 days ago and no progress is made by contributor. @varshitha-besthu if you are interested, pls let us know in issue and create a new PR.

@Adi-204 Adi-204 closed this Sep 30, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Maintainers work Sep 30, 2025
shubham220420 added a commit to shubham220420/generator that referenced this pull request Sep 30, 2025
@derberg derberg moved this from Done to Archive in Maintainers work Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Archive
Development

Successfully merging this pull request may close these issues.

Docs: Add information about baked-in templates (experimental) to main README
3 participants