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

destination_root not used by template function #33

Closed
lennart opened this issue Mar 15, 2010 · 3 comments
Closed

destination_root not used by template function #33

lennart opened this issue Mar 15, 2010 · 3 comments

Comments

@lennart
Copy link

lennart commented Mar 15, 2010

Is there a reason why Thor::Actions::template does not use the destination_root for its destination argument? I thought it would since the documentation says: "relative path to the destination".

Am I misunderstanding the usage of template, or should one explicity pass in File.join(destination_root, filename) as the destination parameter?

@kristianmandrup
Copy link

In my experience it does use the destination root, which is the dir you are in when you call the thor task. If you use the 'inside' command thor will change both destination_dir (target dir for result of templats) and source_dir (where the templates reside).

@lennart
Copy link
Author

lennart commented Mar 16, 2010

ok, the information that the "destination_dir" is the folder you are in when running thor is exactly what I misunderstood. Thanks for clearing that up!

@kristianmandrup
Copy link

I worked all day trying to improve Thor to make it easier and more intuitive to use. Check out my fork ;) I also have a thor task to generate the skeleton for a new thor task, which should make it much easier to get a head start...

http://github.com/kristianmandrup/thortask_generator

Please let me know if you find any bugs, issues or suggestions for further improvement.

This issue was closed.
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