-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Better grunt workflow / local theme.js #1981
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
Comments
see PR #1982 |
I am not so happy with my pull request. I was thinking about auto-detecting the installed themes for grunt. |
I updated my PR #1982 and I am more happy with it now :) - please have a look |
Just a notice: internal ticket MAGETWO-55345 has been created. |
Thank you for your submission. We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues. Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here). We are closing this GitHub ticket and have moved your request to the new forum. |
Hi @amenk , From now you have ability to place local I hope it solves your task. |
@guz-anton: @amenk is really correct in his comment on this change. Using So if you could please get the developers to change this before this is shipped in a new release, that would be great. Otherwise if you only change it after it was shipped in a new release, it would mean that we (yet again) have to change our workflows. Thanks! Completely offtopic, but it made me think of this:
|
When installing a new theme, I would add it to
dev/tools/grunt/configs/themes.js
(according to http://devdocs.magento.com/guides/v2.0/frontend-dev-guide/css-topics/css_debug.html#grunt_prereq)
But this file is in the standard git ignore and would be overwritten when doing a composer update (if Magento is installed via composer)
How can we fix this?
Maybe an additional file custom_themes.js which is included if it exists?
The text was updated successfully, but these errors were encountered: