Explicitly document the licence for the generated code

I’m submitting a…

• Bug report
• Feature request
• Documentation issue or request

Current behavior

The licence for the generated code is not explicitly stated. As there is no strong distinction between the templates from the generators (generator-ngx-rocket or angular-cli) and the generated files, we can assume that the generated code is MIT (same licence as both generators). But it would be better to be explicit, in particular for enterprise users.

Expected behavior

Add an explicit statement in the generator’s documentation. And/or in the generated code ? (in individual files ?, not for the whole generated project, which the user might choose to licence under a different licence)

Great project. Many thanks @sinedied and contributors !

[bursauxa]

I feel like granting such a license would mean that we can 100% guarantee that the entire build chain (angular-cli, webpack, sass, typescript minify, etc etc) does grant you an equivalent license. I mean, if we said “go ahead use our code” but the webpack license itself said “you are free to use webpack but you are forbidden from distributing its output” (it does not - it’s MIT just like this project), our statement would probably infringe on Webpack’s rights, and in turn they could sue us if you distributed code built by webpack through the ngx-rocket scripts. Probably. I am not a lawyer 🤷

[bursauxa]

The Angular guys have not answered this issue in nine months. Closing this as I do no think we could do better than them.