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

Some suggestions to make usage more clear #2

Closed
aligneddev opened this issue Feb 22, 2017 · 2 comments
Closed

Some suggestions to make usage more clear #2

aligneddev opened this issue Feb 22, 2017 · 2 comments

Comments

@aligneddev
Copy link

The flow is confusing at the moment and took me a while to figure out that I had to go to a different directory.

I'd like to be able to go to my directory, then yo ng2component. Instead I had to go up one directory.

Suggestion:

  1. yo ng2component
  2. component or service
  3. Component folder name? (I didn't know that the folder would be the same as the component)
  • instead ask Folder and component name?
  1. Resides location?
  • instead ask "Resides location (/ for current)?" - then make this work (I'm getting errors when I enter /)
  1. Style sheets?
  • once I choose one, please default it to that like the questions above.

Extra request: allow me to choose not to create the index.ts file. I'm going to end up deleting it every time.
Thanks for this generator. I'm using https://github.com/aspnet/JavaScriptServices/ and couldn't figure out how to get the @angular/cli working inside of it. I didn't want to create all these files by hand.

@aligneddev aligneddev changed the title Bring back component name question Some suggestions to make usage more clear Feb 22, 2017
@zzs1020
Copy link
Owner

zzs1020 commented Feb 23, 2017

Hi @aligneddev Kevin, thanks for suggesting so many good ideas.

As you suggested, I've already updated generator-ng2component to version 1.0.9, which includes all new improvements you mentioned.

For question 4, actually you can type . or ./ as current location (should support all unix-style directory format such as .././).

And, you're right, @angular/cli only supports angular-cli-generated-projects, that's the reason why I made this one at the beginning.

Again, thanks for your contributions! If you still find issues for v1.0.9, feel free to contact me. if it looks good to you, let me know and I'll close this ticket.

@aligneddev
Copy link
Author

Thanks for the quick response. This is much improved!

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