generator icon indicating copy to clipboard operation
generator copied to clipboard

How about changing the name of generator and how we call templates

Open derberg opened this issue 4 years ago β€’ 15 comments

Reason/Context

I was just writing an article where I wanted to briefly explain generator and its templates - I failed again. I'm also failing with it always when tweet about it, some generator or template features.

It is ok for projects like https://github.com/OpenAPITools/openapi-generator to call generator a generator because all is contained in a single repo/project

This is the legacy of our generator, in the past is was also a single project. Now "templates" are standalone projects.

maybe simplest would be generator -> generator-core πŸ€” html-template -> html-generator any-template -> any-generator

(as a result, yes, it means renaming packages in npm)

Description

I like how yeoman explains what it is, that what we call "templates" are "generators" and what we call "generator" is "yeoman"

I like this because I also many times talk about html-template as "HTML generator" or "Docs generator".

While it is not a problem to rename html-template to html-generator, obviously it won't be easy to find a name for the generator. There was a good name, but is already taken (fluffy-robot) 😞 πŸ˜†

What do you think?

derberg avatar Apr 29 '21 22:04 derberg

Hmm... I think I am too biased to answer this since it makes perfect sense to me πŸ˜†However for those that do not know the concept of templates (you would have to dig into how the generator work) I can understand if we want to change it.

Therefore I am neither for or against it. Just be aware of the rework that has to be done in order to rename something like this. We are talking documentation, source code variables and structure, npm packages, etc.

jonaslagoni avatar May 03 '21 13:05 jonaslagoni

This issue has been automatically marked as stale because it has not had recent activity :sleeping: It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation. Thank you for your contributions :heart:

github-actions[bot] avatar Jul 03 '21 00:07 github-actions[bot]

maybe simplest would be generator -> generator-core πŸ€” html-template -> html-generator any-template -> any-generator

derberg avatar Jul 05 '21 09:07 derberg

We could name the templates as schematics and leave the generator name :)

magicmatatjahu avatar Jul 05 '21 09:07 magicmatatjahu

and how are schematics different from template? how will this improve the wording and explanation?

@magicmatatjahu

derberg avatar Jul 05 '21 14:07 derberg

I thought you needed a synonym :trollface:

To be honest I have no problem with the name of the generator and with terms such as html generation (from template, not generator) etc. For others people, naming may be a problem, but for me, it's not. Let the others emerge.

magicmatatjahu avatar Jul 05 '21 14:07 magicmatatjahu

This issue has been automatically marked as stale because it has not had recent activity :sleeping: It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation. Thank you for your contributions :heart:

github-actions[bot] avatar Sep 04 '21 00:09 github-actions[bot]

generator -> generator-core πŸ€” html-template -> html-generator any-template -> any-generator

I quite like the rename to generator I think, I guess the generator > template isn't too much of a hurdle, but I'm just used to generator wording.

image

The descriptions for each template say Generates which I guess generator would make more sense?

But as I said not the end of the world, just another hurdle I have to process to initially understand how generator > templates work, think for me anyway generators would make more sense...

boyney123 avatar Sep 06 '21 10:09 boyney123

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

github-actions[bot] avatar Jan 05 '22 00:01 github-actions[bot]

@fmvilas only your opinion is missing. If all codeowners are fine, we could query community

derberg avatar Jan 11 '22 15:01 derberg

I'd not call them "generators". The tool is also called Generator. Are we going to compose sentences like "Use this generator with Generator"? Or another option is that we change the name of tool as well.

fmvilas avatar Jan 11 '22 18:01 fmvilas

they are not called generators, so you would write not Use this generator with Generator but use Node JS Generator either with AsyncAPI CLI or in case of a library, use generator-core library.

So you will say To generate the code in terminal or CI/CD use NodeJS Generator with AsyncAPI CLI. In case you want to do it in a runtime or integrate with your library, use generator-core library

derberg avatar Jan 12 '22 15:01 derberg

Alrighty, sounds good πŸ‘

fmvilas avatar Jan 12 '22 22:01 fmvilas

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

github-actions[bot] avatar May 13 '22 00:05 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

github-actions[bot] avatar Sep 14 '22 00:09 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

github-actions[bot] avatar Jan 14 '23 00:01 github-actions[bot]

yeah, I do not like the name but I do not think the final idea got much attention, we probably have to give it time

derberg avatar Jul 05 '23 17:07 derberg