hygen VS generator

My comment was misleading-I don’t know if Storybook has native support, but using typescript (or Babel, or any parser) you can analyze a component and automatically create stories with good foundational docs. In the past, I’ve used Hygen and a handful of scripts that were tied into our commit workflow that handled generating boilerplate stories for new components and then automatically updated the stories when any changes to props were picked up.

You can look at Hygen: https://github.com/jondot/hygen

this allows you to import this Header component with import { Header } from 'path/Header' without Header/Header. Creating this structure manually is annoying, so one will benefit from some code generators like plop or hygen.

AsyncAPI Generator

With the file created, we can now generate more friendly documentation. For this, we need to install generator or use it in its Docker version.

This can be improved and extended overtime, especially because of the way the generator is designed, enabling extensibility so we can have templates for many other languages that support more protocols, etc. For example, there is only a NATS generator for .NET Core... but perhaps in the future there could be more protocols supported for .NET Core and examples built for Azure 😃.

Continue improvements and add new features to core tools such as our spec parser/validator and code generator.