You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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).
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!
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...
Is there a reason why
Thor::Actions::template
does not use thedestination_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 inFile.join(destination_root, filename)
as the destination parameter?The text was updated successfully, but these errors were encountered: