Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Adding support for custom commands in frontend and setup targets. #195

Merged
merged 10 commits into from
Jun 22, 2016

Conversation

grasmash
Copy link
Contributor

No description provided.

# E.g., ${docroot}/sites/all/themes/custom/mytheme.
dir: ${docroot}
# E.g., `npm install` or `bower install`.
command: echo 'Hello world!'
Copy link
Contributor

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.

Copy link
Contributor Author

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.">
Copy link
Contributor

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...

@grasmash grasmash deleted the custom-tasks branch July 21, 2016 17:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants