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

Pre- and post-processing steps #39

Open
zml2008 opened this issue Sep 24, 2023 · 0 comments
Open

Pre- and post-processing steps #39

zml2008 opened this issue Sep 24, 2023 · 0 comments

Comments

@zml2008
Copy link
Member

zml2008 commented Sep 24, 2023

Right now blossom just emits templates. I'd like to support some sort of system for post-processing to allow, for example, templates to be written in yaml and then converted to json on build, or to apply some sort of autoformatter.

I'm not sure what the most sensible way to handle this is, since the transformers would have to be provided on the worker classpath, and we'd want to pass options through to them.

Do we want a copyspec-type system so certain transformers only apply to certain template files?

These transformers should be able to transform file name and file content, i suppose. Does pebble itself become a transformer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant