Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
220 changes: 110 additions & 110 deletions config/tools-automated.json
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,28 @@
"Code-first tools": {
"description": "The following is a list of tools that generate AsyncAPI documents from your code.",
"toolsList": [
{
"title": "SIO-AsyncAPI",
"description": "This is code-first approach to generate AsyncAPI specification from Socket.IO server.",
"links": {
"websiteUrl": "https://github.com/daler-rahimov/sio-asyncapi",
"docsUrl": "https://github.com/daler-rahimov/sio-asyncapi",
"repoUrl": "https://github.com/daler-rahimov/sio-asyncapi"
},
"filters": {
"language": "Python",
"technology": [
"Socket.IO",
"Flask"
],
"categories": [
"code-first",
"api"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
{
"title": "AsyncAPI.Net",
"description": "The AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common serializers to extract raw OpenAPI JSON and YAML documents from the model.",
Expand Down Expand Up @@ -93,25 +115,6 @@
"isAsyncAPIOwner": false
}
},
{
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "Typescript",
"technology": [
"Node.js",
"NestJS"
],
"categories": [
"code-first"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
{
"title": "AsyncAPI.NET",
"description": "The officially maintained fork of the AsyncAPI.NET SDK contains a useful object model for AsyncAPI documents in .NET along with common (de)serializers to extract raw AsyncApi JSON and YAML documents from the model.",
Expand All @@ -135,22 +138,19 @@
}
},
{
"title": "SIO-AsyncAPI",
"description": "This is code-first approach to generate AsyncAPI specification from Socket.IO server.",
"title": "nestjs-asyncapi",
"description": "Utilize decorators to generate AsyncAPI document utilizing DTOs (similar to @nestjs/swagger) and a web UI.",
"links": {
"websiteUrl": "https://github.com/daler-rahimov/sio-asyncapi",
"docsUrl": "https://github.com/daler-rahimov/sio-asyncapi",
"repoUrl": "https://github.com/daler-rahimov/sio-asyncapi"
"repoUrl": "https://github.com/flamewow/nestjs-asyncapi"
},
"filters": {
"language": "Python",
"language": "Typescript",
"technology": [
"Socket.IO",
"Flask"
"Node.js",
"NestJS"
],
"categories": [
"code-first",
"api"
"code-first"
Comment on lines +141 to +153
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

Fix inconsistent TypeScript casing and missing docsUrl
The language filter is spelled “Typescript” but should be “TypeScript” to match other entries. Also consider adding a docsUrl alongside the repoUrl if this project provides documentation.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 141 to 153, correct the casing of
the language filter from "Typescript" to "TypeScript" to maintain consistency.
Additionally, add a "docsUrl" field next to the existing "repoUrl" under the
"links" section if the project has a documentation URL available, ensuring the
entry includes both repository and documentation links.

],
"hasCommercial": false,
"isAsyncAPIOwner": false
Expand Down Expand Up @@ -470,43 +470,69 @@
"toolsList": [
{
"title": "GitHub Action for Generator",
"description": null,
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"links": {
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
"repoUrl": "https://github.com/asyncapi/cli"
},
"filters": {
"technology": [
"AsyncAPI Generator"
],
"categories": [
"github-action"
"github-actions"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
"isAsyncAPIOwner": true
}
Comment on lines +473 to 486
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

Unify GitHub Action category naming
The first “GitHub Action for Generator” uses "github-actions" but the second uses "github-action". Pick one canonical label (e.g. "github-action") to ensure filters work correctly.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 473 to 486, the category label for
GitHub Actions is inconsistent, using both "github-actions" and "github-action".
Choose one canonical label, such as "github-action", and update all occurrences
to use this exact label to ensure filtering works correctly.

},
{
"title": "GitHub Action for Generator",
"description": "CLI to work with your AsyncAPI files. You can validate them and in the future use a generator and even bootstrap a new file. Contributions are welcomed!",
"description": null,
"links": {
"repoUrl": "https://github.com/asyncapi/cli"
"repoUrl": "https://github.com/actions-marketplace-validations/asyncapi_github-action-for-generator"
},
"filters": {
"technology": [
"AsyncAPI Generator"
],
"categories": [
"github-actions"
"github-action"
],
"hasCommercial": false,
"isAsyncAPIOwner": true
"isAsyncAPIOwner": false
}
Comment on lines 489 to 503
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

Provide description and unify category for second GitHub Action entry
The description is set to null (resulting in no text on the site) and the category label mismatches the first entry. Add a meaningful description or remove the null, and align the categories array with the other entry.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 489 to 503, the GitHub Action entry
has a null description and a category label that does not match the first entry.
Replace the null description with a meaningful text describing the GitHub
Action, and update the categories array to use the same category label as the
first GitHub Action entry to ensure consistency.

}
]
},
"Mocking and Testing": {
"description": "The tools below take specification documents as input, then publish fake messages to broker destinations for simulation purposes. They may also check that publisher messages are compliant with schemas.",
"toolsList": [
{
"title": "ZenWave SDK",
"description": "DDD and API-First for Event-Driven Microservices",
"links": {
"websiteUrl": "https://zenwave360.github.io/",
"docsUrl": "https://zenwave360.github.io/zenwave-sdk/plugins/asyncapi-spring-cloud-streams3/",
"repoUrl": "https://github.com/zenwave360/zenwave-sdk"
},
"filters": {
"language": "Java",
"technology": [
"Maven",
"CLI",
"Spring Cloud Streams",
"JHipster JDL"
],
"categories": [
"code-generator",
"dsl",
"mocking-and-testing",
"cli"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
{
"title": "Mokapi",
"description": "Your API Mocking Tool for Agile Development. Mock and simulate AsyncAPI and OpenAPI services for local testing, development, and CI pipelines — with a visual dashboard to inspect your mocks and a powerful test data generator fully customizable with JavaScript.",
Expand Down Expand Up @@ -549,32 +575,6 @@
"hasCommercial": false,
"isAsyncAPIOwner": false
}
},
{
"title": "ZenWave SDK",
"description": "DDD and API-First for Event-Driven Microservices",
"links": {
"websiteUrl": "https://zenwave360.github.io/",
"docsUrl": "https://zenwave360.github.io/zenwave-sdk/plugins/asyncapi-spring-cloud-streams3/",
"repoUrl": "https://github.com/zenwave360/zenwave-sdk"
},
"filters": {
"language": "Java",
"technology": [
"Maven",
"CLI",
"Spring Cloud Streams",
"JHipster JDL"
],
"categories": [
"code-generator",
"dsl",
"mocking-and-testing",
"cli"
],
"hasCommercial": false,
"isAsyncAPIOwner": false
}
}
]
},
Expand Down Expand Up @@ -692,21 +692,24 @@
"description": "The following is a list of tools that you can work with in terminal or do some CI/CD automation.",
"toolsList": [
{
"title": "Mokapi",
"description": "Your API Mocking Tool for Agile Development. Mock and simulate AsyncAPI and OpenAPI services for local testing, development, and CI pipelines — with a visual dashboard to inspect your mocks and a powerful test data generator fully customizable with JavaScript.",
"title": "ZenWave SDK",
"description": "DDD and API-First for Event-Driven Microservices",
"links": {
"websiteUrl": "https://mokapi.io",
"docsUrl": "https://mokapi.io/docs/guides/welcome",
"repoUrl": "https://github.com/marle3003/mokapi"
"websiteUrl": "https://zenwave360.github.io/",
"docsUrl": "https://zenwave360.github.io/zenwave-sdk/plugins/asyncapi-spring-cloud-streams3/",
"repoUrl": "https://github.com/zenwave360/zenwave-sdk"
},
"filters": {
"language": "Go/Golang",
"language": "Java",
"technology": [
"JavaScript",
"TypeScript",
"Docker"
"Maven",
"CLI",
"Spring Cloud Streams",
"JHipster JDL"
],
"categories": [
"code-generator",
"dsl",
"mocking-and-testing",
"cli"
],
Expand All @@ -715,24 +718,21 @@
}
},
{
"title": "ZenWave SDK",
"description": "DDD and API-First for Event-Driven Microservices",
"title": "Mokapi",
"description": "Your API Mocking Tool for Agile Development. Mock and simulate AsyncAPI and OpenAPI services for local testing, development, and CI pipelines — with a visual dashboard to inspect your mocks and a powerful test data generator fully customizable with JavaScript.",
"links": {
"websiteUrl": "https://zenwave360.github.io/",
"docsUrl": "https://zenwave360.github.io/zenwave-sdk/plugins/asyncapi-spring-cloud-streams3/",
"repoUrl": "https://github.com/zenwave360/zenwave-sdk"
"websiteUrl": "https://mokapi.io",
"docsUrl": "https://mokapi.io/docs/guides/welcome",
"repoUrl": "https://github.com/marle3003/mokapi"
},
"filters": {
"language": "Java",
"language": "Go/Golang",
"technology": [
"Maven",
"CLI",
"Spring Cloud Streams",
"JHipster JDL"
"JavaScript",
"TypeScript",
"Docker"
],
"categories": [
"code-generator",
"dsl",
"mocking-and-testing",
"cli"
],
Expand Down Expand Up @@ -869,18 +869,19 @@
"description": "The following is a list of templates compatible with AsyncAPI Generator. You can use them to generate apps, clients or documentation from your AsyncAPI documents.",
"toolsList": [
{
"title": "Java Spring Cloud Stream Template",
"description": "Java Spring Cloud Stream template for the AsyncAPI Generator",
"title": "Java Spring Template",
"description": "Java Spring template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
"repoUrl": "https://github.com/asyncapi/java-spring-template"
},
"filters": {
"language": [
"javascript"
],
"technology": [
"Spring Cloud Streams",
"Maven"
"Springboot",
"Maven",
"Gradle"
Comment on lines +872 to +884
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

Correct language filter for Java Spring Template
The language is set to ["javascript"] but this is a Java template. Update to ["Java"] to ensure it appears under the correct filter.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 872 to 884, the language filter for
the Java Spring Template is incorrectly set to ["javascript"]. Change this value
to ["Java"] to correctly categorize the template under the Java language filter.

],
"categories": [
"generator-template"
Expand All @@ -890,10 +891,10 @@
}
},
{
"title": "Node.js Websockets Template",
"description": "Node.js WebSockets template for the AsyncAPI Generator. It showcases how from a single AsyncAPI document you can generate a server and a client at the same time.",
"title": "Node.js Multiprotocol Template",
"description": "This template generates a server using your AsyncAPI document. It supports multiple different protocols, like Kafka or MQTT. It is designed in the way that generated code is a library and with it's API you can start the server, send messages or register a middleware for listening incoming messages. Runtime message validation included.",
"links": {
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
"repoUrl": "https://github.com/asyncapi/nodejs-template"
},
Comment on lines +894 to 898
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

Standardize language filter type for Node.js Multiprotocol Template
Use an array for language (e.g. ["JavaScript"]) rather than a string, and capitalize “JavaScript” to match the site’s conventions.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 894 to 898, the language filter for
the Node.js Multiprotocol Template is currently a string and uses lowercase
"javascript". Change the language field to be an array containing the
capitalized string "JavaScript" to standardize the format and match site
conventions.

"filters": {
"language": "javascript",
Expand All @@ -908,15 +909,15 @@
}
},
{
"title": "HTML Template",
"description": "HTML template for AsyncAPI Generator. Use it to generate a static docs. It is using AsyncAPI React component under the hood.",
"title": "Node.js Websockets Template",
"description": "Node.js WebSockets template for the AsyncAPI Generator. It showcases how from a single AsyncAPI document you can generate a server and a client at the same time.",
"links": {
"repoUrl": "https://github.com/asyncapi/html-template"
"repoUrl": "https://github.com/asyncapi/nodejs-ws-template"
},
Comment on lines +912 to 916
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

Standardize language filter type for Node.js Websockets Template
Convert language from a string to ["JavaScript"] and use the proper casing.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 912 to 916, the language filter for
the Node.js Websockets Template is currently a string and not standardized.
Change the language field from a single string to an array containing
"JavaScript" with proper casing, i.e., ["JavaScript"], to maintain consistency
with other entries.

"filters": {
"language": "javascript",
"technology": [
"HTML"
"Node.js"
],
"categories": [
"generator-template"
Expand All @@ -926,19 +927,17 @@
}
},
{
"title": "Java Spring Template",
"description": "Java Spring template for the AsyncAPI Generator",
"title": "Java Template",
"description": "Java template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-spring-template"
"repoUrl": "https://github.com/asyncapi/java-template"
},
Comment on lines +930 to 934
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

Fix language filter for Java Template
The language is currently ["javascript"] but should be ["Java"].

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 930 to 934, the language filter for
the Java Template is incorrectly set to ["javascript"]. Change the language
value to ["Java"] to correctly reflect the template's language.

"filters": {
"language": [
"javascript"
],
"technology": [
"Springboot",
"Maven",
"Gradle"
"Java"
],
"categories": [
"generator-template"
Expand All @@ -948,17 +947,18 @@
}
},
{
"title": "Java Template",
"description": "Java template for the AsyncAPI Generator",
"title": "Java Spring Cloud Stream Template",
"description": "Java Spring Cloud Stream template for the AsyncAPI Generator",
"links": {
"repoUrl": "https://github.com/asyncapi/java-template"
"repoUrl": "https://github.com/asyncapi/java-spring-cloud-stream-template"
},
"filters": {
"language": [
"javascript"
],
"technology": [
"Java"
"Spring Cloud Streams",
"Maven"
Comment on lines +950 to +961
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

Fix language filter for Java Spring Cloud Stream Template
Update language from ["javascript"] to ["Java"] to reflect the actual template language.

🤖 Prompt for AI Agents
In config/tools-automated.json between lines 950 and 961, the language filter
for the Java Spring Cloud Stream Template is incorrectly set to ["javascript"].
Change the language filter value to ["Java"] to correctly represent the
template's programming language.

],
"categories": [
"generator-template"
Expand All @@ -968,15 +968,15 @@
}
},
{
"title": "Node.js Multiprotocol Template",
"description": "This template generates a server using your AsyncAPI document. It supports multiple different protocols, like Kafka or MQTT. It is designed in the way that generated code is a library and with it's API you can start the server, send messages or register a middleware for listening incoming messages. Runtime message validation included.",
"title": "HTML Template",
"description": "HTML template for AsyncAPI Generator. Use it to generate a static docs. It is using AsyncAPI React component under the hood.",
"links": {
"repoUrl": "https://github.com/asyncapi/nodejs-template"
"repoUrl": "https://github.com/asyncapi/html-template"
},
"filters": {
"language": "javascript",
"technology": [
"Node.js"
"HTML"
Comment on lines +971 to +979
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

Standardize language filter type for HTML Template
Switch language from a string to an array (e.g. ["JavaScript"]) and use consistent casing.

🤖 Prompt for AI Agents
In config/tools-automated.json around lines 971 to 979, the language filter for
the HTML Template is currently a string with inconsistent casing. Change the
"language" field from a string to an array containing "JavaScript" with proper
capitalization, i.e., ["JavaScript"], to standardize the filter type and casing.

],
"categories": [
"generator-template"
Expand Down
Loading
Loading