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.

Sign up for GitHub

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

Jump to bottom

What to do on breaking changing updates? #433

Open

greatestview opened this issue Apr 18, 2017 · 0 comments

Assignees

Labels

core prio 1 refactoring

Contributor

greatestview commented Apr 18, 2017

We have to think about what to do, when we commit breaking changes in our Template or CSS system.

@EdwardBock mentioned the WooCommerce way:

No legacy support setting.
Better: Grid could check the number of template files in the theme folder and suggest to copy the remaining old template files into the theme to maintain backwards compatibility.
Version numbers in the template files?
No legacy fallback support inside the templates, the templates should stay clean.

greatestview added core prio 1 refactoring labels

greatestview assigned EdwardBock

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