-
Notifications
You must be signed in to change notification settings - Fork 9
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
Allow custom templates #4
Comments
@atifsyedali
These variables appear in the template prefixed with an $, like for example: Is this simple home grown template system sufficient for your needs or do need a more elaborated template system? |
Hi, It would have been nice to allow input of a file and keep those three variables. So for example, I have a copyright header that looks like... copyrightFile.txt in my project's root: /*******************************************************************************
* © $copyrightHolder, $from-$to
* All Rights Reserved.
******************************************************************************/ and then in the input you can just do |
@atifsyedali This should be actually a simple change, but unfortunately I have zero time this week. |
@shybyte TBH I started this change but then someone pointed to me https://github.com/Stuk/eslint-plugin-header so I have switched over to that. I am going to create a PR with what I have so far. |
@atifsyedali, I too looked at both of these options. I'm surprised you switched over to https://github.com/Stuk/eslint-plugin-header. It offers custom templates, but does not offer good handling of date ranges. To my knowledge, it also does not support any analysis of
|
I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
Allow specifying a custom template by pointing to a template file.
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
The text was updated successfully, but these errors were encountered: