feat(component): add less support

[wesleycho]

• Add optional support for less via style option

[cironunes]

we need a test for this

[cironunes]

Thanks @wesleycho, I liked the approach.
We need tests for the generate command and I added a few comments, otherwise it's good to merge.

[wesleycho]

Alright, I'll take a look today at writing the tests - might not get to it for a few days.

The approach is a bit hackish since it rewrites the file name after install, but I couldn't think of anything better.

[cironunes]

Yes, we might have template files in the future, but I'm ok with this for now.

[wesleycho]

I added tests, still need to implement that change to only compile the less if less is present, pending answer to question.

[filipesilva]

There was been talk of a angular2-config.json or a similar file. This sort of configuration would belong there I'd say.

[filipesilva]

Also, there seems to be some trouble with newly generates files #120 (comment)

[Brocco]

As of now the idea of configuration has been moved into package.json adding the style option should be placed here: https://github.com/angular/angular-cli/blob/master/addon/ng2/blueprints/ng2/files/package.json#L5-L9

[intellix]

just wondering how this is optional support (as I'd like to have SASS instead) :)
broccoli-less is added to package.json and the LESS compilation is added to angular2-app.js. For this to be optional, wouldn't it have to be added as an additional addon that was separate to this project?

[hansl]

This feels like something that we should support properly but need design beforehand.

We need to let the user choose, and I think ng install is the right place for this logic. Using something like ng install less for example, changing the build and the scaffolding, would be great. From that point the user would create components that use less and build less when he runs ng serve. I could also see an ng install sass coming after the first one and we generate an error with something like "you are already using a build library that targets the same kind of files; use both? Y/n".

I'm reworking the specs of ng install right now and this particular usage will be taken into account.

I think this PR should be closed as this will never be something we support natively. There should not be a force of technology that the user has to pick (outside of the cli itself, of course). I could even see a point where we don't force the user to use TypeScript if he doesn't want to, and generate JavaScript components. I had a ng use kind of command for this, but this could be built into ng install.

[wesleycho]

I'm in agreement - even my refactor I have locally still is a bit incorrect.

This probably needs a whole spec and maybe a plugin implementation.

[hansl]

Wes, you'll be in on the discussion for the ng install, and you'll definitely be welcome to do any work necessary to support less.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}