Skip to content
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.

Add SASS Support #19

Open
aubreypwd opened this issue Feb 4, 2019 · 1 comment
Open

Add SASS Support #19

aubreypwd opened this issue Feb 4, 2019 · 1 comment

Comments

@aubreypwd
Copy link
Owner

I, simply, should be able to write SASS. And when I save it a .css version of it is made so I can enque it.

@aubreypwd aubreypwd added the CSS label Feb 4, 2019
@aubreypwd aubreypwd added this to the 2.1.0 milestone Feb 4, 2019
@aubreypwd
Copy link
Owner Author

aubreypwd commented Feb 4, 2019

@efuller Also getting you involved here as promised....

I could probably build this out but you could probably do this a lot better than I would.

Here's my initial thoughts on this too:

First off I am not a fan of compiling tons of SASS files down to one file, but I'm not saying that's wrong, I'm just not a fan. I like enqueuing stuff when I use them, e.g. I build services/my-service/assets/styles/my-styles.sass and I want a services/my-service/assets/styles/my-styles.css file made right beside it. That way I could enqueue right then, the piece I want...

But that doesn't mean I don't want you to be able to compile many SASS files into one CSS file. If you wanted to. I'm not sure how we would do both or how one would architect their SASS so that it would build down into one file somehow e.g. via indexes?

Either way I would like that tool to be able to do either, depending on how you build our your SASS in your service/component. Just like #18 we need this tool to work with SASS written in components or services.

Also want to discuss further, just my initial thoughts on this.

@aubreypwd aubreypwd assigned aubreypwd and unassigned aubreypwd Feb 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant