Skip to content
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

Clarify what lineman plugins should do #235

Open
Foxandxss opened this issue Mar 22, 2014 · 1 comment
Open

Clarify what lineman plugins should do #235

Foxandxss opened this issue Mar 22, 2014 · 1 comment

Comments

@Foxandxss
Copy link
Contributor

Creating a new plugin with a custom task under /tasks is not working (see Foxandxss/lineman-protractor#2).

There is something wrong on the core, we should investigate that.

@davemo
Copy link
Member

davemo commented Jan 27, 2015

I think there's a higher level discussion we should have about what role plugins should play and whether supporting the /tasks folder is part of that. Right now plugins are pretty much simple grunt config mutators but with the creation of the lineman-vendor-split plugin and #344 perhaps we should revisit what plugins should do.

My $0.02 is that they should be as unintelligent as possible :)

@davemo davemo changed the title Creating plugins with tasks on /tasks Clarify what lineman plugins should do Jan 27, 2015
@davemo davemo added the plugins label Jan 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants