generator icon indicating copy to clipboard operation
generator copied to clipboard

Proof of concept of templates as part of generator monorepo

Open derberg opened this issue 1 year ago • 8 comments

We know we want to have some core templates developed under this repo, as a result of:

  • https://github.com/asyncapi/generator/issues/1249
  • https://github.com/asyncapi/generator/issues/1044

This PoC needs to answer questions like:

  • do we need to release such internal templates separately, as npm modules
  • how generator release relates to template release
  • how it will be used in the AsyncAPI CLI
  • do we keep name templates? or leave it only for extensibility part?
  • maybe https://github.com/asyncapi/nodejs-template could be moved as an example - not 100% sure as it may make things complex for review
  • how shared helpers will be maintained and tested
  • how shared components will be maintained and tested
  • should helpers and components be released as independent package? so template developers that write templates outside, can still use these. For example instead of telling people https://www.asyncapi.com/docs/tools/generator/model-generation we could have a build in components for types generation, so people do not really have to even know what modelina is and add it to dependencies
  • how testing is split

Resulting PR not necessarily needs to be merged, but should be in state that helps to followup with exact implementation

derberg avatar Sep 16 '24 11:09 derberg