Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fork scaffolding logic into yeoman generator #62

Closed
maxmalov opened this issue Nov 3, 2014 · 3 comments
Closed

Fork scaffolding logic into yeoman generator #62

maxmalov opened this issue Nov 3, 2014 · 3 comments

Comments

@maxmalov
Copy link

maxmalov commented Nov 3, 2014

Let assume that all migration logic are moved to a separate package to easily create grunt/gulp plugins (#5). But there is also need help with generation configs/models/migrations etc. For example, there is a generate script in the RoR world. Scaffolding is out of the tasks related logic there. Most of js developers already use task runner, some part of them is using yeoman generators. Having a third different tool that combines task related and scaffolding logic can make things slightly confusing.

For example, generator could provide the following (assume it named generator sequelize):

  • this will ask where to store configs, models, migrations and create a structure based on answers:
yo sequelize
  • this will create config at the specified location:
yo sequelize:config

and so on. What does you think about that?

@sdepold
Copy link
Member

sdepold commented Nov 3, 2014

I could live with that :D

@maxmalov
Copy link
Author

maxmalov commented Nov 3, 2014

Oh, it seems that I suck at convincing people :| ))

@sdepold
Copy link
Member

sdepold commented Jan 18, 2015

I was actually thinking about moving the "core logic" of the cli to another promise based package which is then triggered by the current gulp structure. closing this ticket for now. feel free to re-open it if there is something else to discuss.

@sdepold sdepold closed this as completed Jan 18, 2015
codetriage-readme-bot pushed a commit to codetriage-readme-bot/cli that referenced this issue Jun 5, 2019
Display error message received from fetch current endpoint
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants