-
-
Notifications
You must be signed in to change notification settings - Fork 495
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
Default change: dataTemplateEngine: false
in Configuration Object
#174
Comments
The other thing here is the #155 |
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. The enhancement backlog can be found here: https://github.com/11ty/eleventy/issues?utf8=%E2%9C%93&q=label%3Aneeds-votes+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! |
I never knew it was a feature and if it's a performance hit, I'd be in favor of this. You could do the same with a .js file instead of .json, right? So if you can get the same result, I'd say go ahead. |
Well, it's the first major version so breakage is allowed. I guess you can't really see how many users have this currently enabled, but we could check the submitted starter templates (as most start with those) and base on that? If a significant amount of starters don't use it then it makes sense especially if there's a performance hit. |
As clarification we would only turn this off by default. You could opt-back in very easily with config https://www.11ty.dev/docs/config/#default-template-engine-for-global-data-files |
Default change of |
Docs added at 11ty/11ty-website@607f9d8 |
Deprecation warning added 11ty/11ty-website@0a3bf7c |
For performance reasons.
This appears to be an underutilized feature and could be disabled by default. If you make use of data preprocessing, please chime in here!
The text was updated successfully, but these errors were encountered: