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
Expose the directory where the generator is being executed #982
Conversation
Can someone relaunch the checks? There was a timeout on one of them that has nothing to do with that PR. |
Restarted Node 6. |
@mischah Thanks a lot! |
Please give the pull request a descriptive title ;) |
Done. I also clarified the description. |
So, |
That's exactly the point of the issue #947 . |
To go further on that point, I didn't want to change the behavior of That's why I did add a new property to store the initial value of |
Thanks for the answer. I missed that line reading through the code yesterday. Sounds good to merge :) |
I'm not sure about how to update the documentation. Should I create an issueand PR now on yeoman/yeoman.github.io or should I wait for the version that contains that PR to be released? |
Hej @ericmorand, open now and reference yeoman/yeoman.io#700 Thanks for your help |
Even better: |
This PR propose an elegant solution to issue #947.
By exposing the directory where the generator was executed, we give the opportunity to subgenerators to scaffold into the current folder instead of the project folder.
Tests have been implemented. I hope the name
contextRoot
for the property is OK to everyone.