-
-
Notifications
You must be signed in to change notification settings - Fork 491
-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Strategies to help developers mitigate breaking changes in 1.0 #1322
Comments
References to Liquid #1334. |
Default to including all items from pagination in |
@zachleat I understand you still think breaking changes in the 1.0 release don't need any previous deprecation/change warning in an intermediate release? I know some of the changes I would like to see won't be in 1.0, so I'll have to wait for a 2.0… 😅 |
I plan to do as much runtime communication in 1.0 as possible. #1390 will be a good example of this. If we detect |
Look for INPUT DIR (if not same as ROOT DIR) |
Some work has started on this here: https://github.com/11ty/eleventy-upgrade-help |
Switching to #1393 as the home base for this one! Subscribe over there if you’d like! |
There are multiple things that could be done to enhance Eleventy but require breaking changes.
Would it make sense to release a 0.12.0 version to prepare these breaking changes before they happen in version 1.0?
A build in this 0.12.0 could then generate deprecation/change warnings in the console, without actually changing anything from 0.11.0.
Changes I have in mind:
slugify
function: Slug filter doesn't create url safe slugs. #278 (comment)addWatchTarget
even if they are in.gitignore
or.eleventyignore
? (maybe): Allow addWatchTarget to watch ignored files #893 (comment)inputPath
in transforms #789 (comment)Feel free to comment to add others!
The text was updated successfully, but these errors were encountered: