generator
generator copied to clipboard
Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
#### Describe the bug When trying to run a project that uses ts-node AND async-api generator, the following error appears. ``` Users/x/async-api-nest/node_modules/@asyncapi/generator/node_modules/ts-node/src/index.ts:513 return new TSError(diagnosticText, diagnosticCodes) ^ TSError: ⨯ Unable...
We should integrate new ParserAPI in Generator but with fallback compatibility with old one, solution described in the https://github.com/asyncapi/parser-js/issues/585: - add support for new (optional!) field in template's config, `apiVersion`...
[test_output.tar.gz](https://github.com/asyncapi/generator/files/13398068/test_output.tar.gz) **Description** Use npm config values in arborist in order to inherit form the global config when pulling a template. This allow to pass config like private registry and proxy-auth....
## Current state - https://github.com/asyncapi/generator/ that is a core - https://github.com/asyncapi/generator-react-sdk for react render engine - https://github.com/asyncapi/generator-filters/ with shared filters - https://github.com/asyncapi/generator-hooks/ with shared hooks - Multiple repositories with templates...
#### Describe the bug `ts-node` is registered if `@asyncapi/generator` is simply imported in a file, even though the constructor or any other of `generator`'s methods is not called at all....
**Description** I added `$$operation$$` as a file template. **Related issue(s)** #1116
#### Describe the bug I originally stumbled upon this bug when I started using `nestjs-asyncapi` package (https://github.com/flamewow/nestjs-asyncapi/issues/516). Importing one of their decorators resulted in wrong call stack for failing tests....
#### Describe the bug Everyday github runs a workflow based on [templates-list-validator](https://github.com/asyncapi/generator/blob/master/.github/workflows/templates-list-validation.yml) . The bug here is that this workflow runs on every forked repository also, which I think is...
I am using AsyncAPI in conjunction with cloudevents. For this the default content type as for media I chose as "application/cloudevents+json" as per the official cloudevent spec https://github.com/cloudevents/spec/blob/main/cloudevents/formats/json-format.md. Accordingly, I...
#### Describe the bug It looks like the generator cannot handle types that are referenced in other files. Declaring the type locally in the schemas section works perfectly, but not...