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
Starting from cookiecutter 2.2 and surely on 2.4 the example of dictionary variables from the docs doesn't work anymore.
I should probably say: It doesn't work as I was used to using it... and it seemed perfectly reasonable to me.
It seems that the current implementation doesn't allow anything not written in cookiecutter.json while up to 2.1.1 you could just give a template of what you would have added. In the example docs, if you wanted to add different file_types you could just pass them in the context (when working from Python script) and it just worked.
Now we completely lost any dynamicity, you have to write down all the possibilities in advance, which is not an option in many cases.
Let me know if I just overlooked the docs and missed how to add dynamicity, if not please consider how many people were relying on that feature or could benefit from that feature. I could provide tons of examples... currently, I was looping on users on docker services, on ports, on files... all this just stopped working.
The docs say "Dictionary variables provide a way to define deep structured information when rendering a template.".
It states structure not data! The current implementation meddles with data, you can't send a file_type if not in cookiecutter.json
If I understood correctly the move with 2.2 was to create a nested choice type (please tell me if I'm wrong), but that should not be as the expenses of the possibility already there from 1.5+ to loop on dynamic values.
BTW: If I create an extra_context that only has one file_type, the other is added anyhow, I would consider this definitely a bug
The text was updated successfully, but these errors were encountered:
Starting from cookiecutter 2.2 and surely on 2.4 the example of dictionary variables from the docs doesn't work anymore.
I should probably say: It doesn't work as I was used to using it... and it seemed perfectly reasonable to me.
It seems that the current implementation doesn't allow anything not written in
cookiecutter.json
while up to 2.1.1 you could just give a template of what you would have added. In the example docs, if you wanted to add different file_types you could just pass them in the context (when working from Python script) and it just worked.Now we completely lost any dynamicity, you have to write down all the possibilities in advance, which is not an option in many cases.
Let me know if I just overlooked the docs and missed how to add dynamicity, if not please consider how many people were relying on that feature or could benefit from that feature. I could provide tons of examples... currently, I was looping on users on docker services, on ports, on files... all this just stopped working.
The docs say "Dictionary variables provide a way to define deep structured information when rendering a template.".
It states structure not data! The current implementation meddles with data, you can't send a file_type if not in
cookiecutter.json
If I understood correctly the move with 2.2 was to create a nested choice type (please tell me if I'm wrong), but that should not be as the expenses of the possibility already there from 1.5+ to loop on dynamic values.
BTW: If I create an
extra_context
that only has onefile_type
, the other is added anyhow, I would consider this definitely a bugThe text was updated successfully, but these errors were encountered: