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

Need a Yeoman generator? #135

Closed
hwclass opened this issue Dec 9, 2015 · 12 comments
Closed

Need a Yeoman generator? #135

hwclass opened this issue Dec 9, 2015 · 12 comments

Comments

@hwclass
Copy link

hwclass commented Dec 9, 2015

Hi there,

Do you think that T3 needs a Yeoman generator to generate some modules, services and behaviors?

Looking for some interesting ideas,

Thanks,

Barış Güler

@nzakas
Copy link
Contributor

nzakas commented Dec 9, 2015

I think a Yeoman generator would be a great addition to the ecosystem. We have one internally but it's really specific to how our app is setup. Are you interested in creating a general purpose T3 Yeoman generator?

@hwclass
Copy link
Author

hwclass commented Dec 9, 2015

Yes, I am interested in to create a yeoman generator. I am also planning to create a sample T3 demo working with React components. So it would be useful to create a generator to use the library with other middlewares included easily as well.

@hwclass
Copy link
Author

hwclass commented Dec 10, 2015

Ok, then. Can you conduct for where to start? For example, if we think that we can create a Yo generator, it is needed to suggest on an ideal project structure for that creation process. For example, if I generate a service by typing in terminal as "yo t3js", where do you think that is the best place for creating the services (by typing "yo t3js:service dummyService") for example? I think that the project structure is basically can be structured or can be parametrized by yeoman console.

@hwclass
Copy link
Author

hwclass commented Dec 10, 2015

Or maybe we can start by creating a new directory in this repository as "generator-t3js"... Looking for the comments and ideas as well ;) Thanks for your patience :)

@nzakas
Copy link
Contributor

nzakas commented Dec 10, 2015

I think you want to ask where JavaScript files belong, and then create services, modules, and behaviors as subdirectories under that directory.

@zephraph
Copy link
Contributor

Here's my perspective:

yo t3: Generate out specified modules, services, and behaviors in subdirectories at the desired location.
yo t3:[module|service|behavior]: Generate a the specified item in the desired directory (defaulting to the current working directory).

@hwclass
Copy link
Author

hwclass commented Dec 11, 2015

The latest proposal is fine I think.

"yo t3" : The creation for the project structure
"yo t3 : [module|service|behavior] name" : The creation for the specified addition (exm: yo t3 : module textEditor)

Do you all think that fit the needs? Then I can make a pull request the first step for yeoman generator of the framework...

Thanks.

@zephraph
Copy link
Contributor

At the very least I think that's a good starting point. @nzakas should the generator be in its own repo?

@nzakas
Copy link
Contributor

nzakas commented Dec 11, 2015

@zephraph yes. We are happy to provide guidance but can't manage the generator at this time.

@zephraph
Copy link
Contributor

👍

@zephraph
Copy link
Contributor

@hwclass I feel like we should close this issue. If you create a repo for the generator feel free to link it back here.

@nzakas
Copy link
Contributor

nzakas commented Jan 13, 2016

Good idea @zephraph

@nzakas nzakas closed this as completed Jan 13, 2016
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

3 participants