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

Specify Stylesheet Path in Config #111

Open
scottmcpherson opened this issue Mar 10, 2015 · 2 comments
Open

Specify Stylesheet Path in Config #111

scottmcpherson opened this issue Mar 10, 2015 · 2 comments

Comments

@scottmcpherson
Copy link
Contributor

For sass users, it would be nice to be able to specify the path at which stylesheets are generated.
To do this, we would probably need to have the concept of variables within a path. The default could look like this:

{
    "stylesheet": {
        "path": "/client/templates/$template-name/"
     }
}

For sass, it would look something like:

{
    "stylesheet": {
        "path": "/client/sass/pages/"
     }
}

Excluding the $template-name variable would prevent the stylesheet generator from creating an additional folder (named whatever the template name is).

In the generator, we could just tear down the path from the config file and reconstruct it with the correct values.

@cmather
Copy link
Contributor

cmather commented Mar 10, 2015

Interesting idea. Maybe people customize the location of their stylesheets enough that having a configurable path option like this is a good idea. But what about generating stylesheets at a given path with the command itself - iron g:stylesheet some/path/to/stylesheet.less

@scottmcpherson
Copy link
Contributor Author

That could work too. But it might get a little redundant for bigger apps.
Or maybe this would be better off in a packaged/pluggable generator.

I'm just trying to think in terms of high level flexibility. And if the path is the only thing that needs to be customized to enable the sass developer to efficiently create sass sheets, then it might not be a bad idea to have it in there as a quick one line modification.

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