Plugin/extension system about cookiecutter HOT 9 CLOSED

I have somewhat run into a need for this as I have a template with some repeated, complicated Jinja templating that I don't want to make into one explicit Jinja plugin that people have to depend on so as to not gain a dependency on my template. It would be great if from some hook I could directly manipulate the Jinja context to inject my own items and plugins.

from cookiecutter.

Okay, cool. 🙇

I've used jinja2 assignments to help with that, but as you say, it doesn't work across multiple files.

Thanks for the feedback, I'll take it into consideration when we design a plugin system.

from cookiecutter.

You mention Danny's secret key plugin, but it appears the plugin itself is a secret? :-) I'd love to see it - secret key generation (and other similar extensions) would be quite nice.

from cookiecutter.

Is anyone opposed to setuptools entry points for handling this?

I'm going to assume the most natural place to something like this is for users to write their own Jinja2 Extensions so the custom tags can be used in their templating.

At first glance it doesn't seem too difficult to implement, I'd be happy to give it a go. Would pretty much just need to load everything in generate_files and set the extensions=[...] in the Jinja Environment initialization.

The other problem is Jinja Extensions are not exactly straight forward if you haven't done them before. Maybe start off with just simple Jinja Extenions, and then slowly over time add some CC helpers to make authoring them a little more straight forward in common cases?

from cookiecutter.

See Pull Request #103

from cookiecutter.

Hi @brettcannon! 👋

Would your "own items and plugins" have any dependencies (other than what is already required by cookiecutter itself)?

from cookiecutter.

Nope. Honestly I just want a way to add more items programmatically after the user has entered their info.

To put this in concrete terms, I'm doing {{ cookiecutter.python_version|replace('.', '')|truncate(2, end='') }} across two files in multiple places (setting a variable when I can, but I'm still doing it multiple files), so I would rather do that manipulation in my pre-hook in Python code and store the result in the cookiecutter object so I could then access it from the Jinja code. So no dependencies at all since it's just straight-forward string manipulation that would be easier in Python than Jinja.

from cookiecutter.

I think this falls under the same category as #848. Assigning the Requires Sponsorship label until we have sponsorship for this project.

from cookiecutter.

@jensens @pydanny @ssbarnea This issue is 10 years old. I recommend closing the issue.

from cookiecutter.