Added: Path templates will be rendered when copy_without_render used#839
Conversation
09ed9a3 to
0e4a9b8
Compare
|
Any chance to see that one merged ? It would be great !!! |
|
Hi !
Any review, any comment, I'll make the changes ASAP ! |
|
I think it looks good @noirbizarre |
|
@noirbizarre could we please have a small update to the docs to include a note about the path vs file content behaviour of this functionality. |
0e4a9b8 to
b0d7235
Compare
|
Done. |
b0d7235 to
93a55d4
Compare
hackebrot
left a comment
There was a problem hiding this comment.
Looks good! Thank you 🙇
Minor docs fix.
|
I wonder if we should treat this as a breaking change... 🤔 |
93a55d4 to
d6df586
Compare
|
I fixed the typo. My opinion: I don't think this should be considered as a breaking change but as a fix because the previous behavior was inconsistent (different behavior for files and directories) and unless you are making a meta cookiecutter (ie. a cookiecutter template rendering cookiecutter templates), I don't think there is any reason to render brackets into path (which was the behavior for directories before this fix because path variables were not rendered). |
|
@audreyr @pydanny @michaeljoseph @theodesp @hackebrot |
d6df586 to
840844d
Compare
|
@noirbizarre Thank you for contribution. Nothing lost. Merged after 4 year in queue :) |
|
Thanks for this change. |
This pull-request ensures paths variables are rendered when using
_copy_without_render.It should fix #456.
It does not keep the existing behavior as it was inconsistent, different for files and directories (matched files had their path rendered but not the matched directories).
If this behavior should be kept, I'll update this pull-request with a boolean option like
_copy_without_render_paths.