-
Notifications
You must be signed in to change notification settings - Fork 394
Adding support for custom commands in frontend and setup targets. #195
Conversation
# E.g., ${docroot}/sites/all/themes/custom/mytheme. | ||
dir: ${docroot} | ||
# E.g., `npm install` or `bower install`. | ||
command: echo 'Hello world!' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not crazy about "Hello world" here.
I think it could be confusing to see it go past during a build, out of context.
I'd rather see something like echo 'Frontend build not configured.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea.
<foreach list="${project.themes}" param="frontend.theme" target="frontend:build:run"/> | ||
</then> | ||
</if> | ||
<target name="frontend:build" description="Uses gulp to build front end dependencies for all themes."> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description here feels a bit misleading to me. As a user I might expect there to already be some magic built in to find and compile my sass files with gulp. It's not clear by the description that I would need to define the command in my project.yml file. Unless I'm missing something which very well could be the case...
No description provided.