I'd like to confirm how I 'should' be using the new license feature with my own templates.
I specify :license/id "MIT" in the template.edn file for the project template. This makes information available about the license, via keys such as :license/name and :license/url, which I can include in source code and docs using the usual {{ }} substitution approach.
If I want to include a LICENSE file with the full text of the specified licence in the generated project, the template should have a LICENSE file which contains the {{license/text}} for substitution.
A license file is not created when only specifying :license/id "MIT" in the template.edn
Please correct anything I have not understood correctly. Thank you.
All your statements look correct to me.
If you want your template to generate an MIT license by default then template.edn is indeed the place where you set :license/id "MIT" to override the default of EPL-2.0 set by deps-new .
@jr0cket If you have suggestions for improving the README around that, feel free to submit a PR.