-
Notifications
You must be signed in to change notification settings - Fork 3
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
Template renaming should not be exclusive to components #32
Comments
i'll work on this one, maybe i'll come up with something in the next hour or so |
i'm not able to get the |
The |
Seems like the others do not work anymore.. i'll see what i can do :) |
pushed a first draft into #34 |
You rock 🚀, thanks for contributing in the first place. I've also added a feature request #36 to work on the examples and make them more meaningful in the future. |
#32: Template renaming should not be exclusive to components
Currently, the templater only allows renames for component rendering.
But it would be nice to be able to expose that functionality to the other template rendering methods
Execute
andExecuteAll
.This would introduce just a small change and generalise the use of Skipper even more.
The text was updated successfully, but these errors were encountered: