Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Suggestion] Choose template for update

See original GitHub issue

One feature I am in general missing in generate/update:

Let’s say I have different project types
Depending on the project type I’d like to add different templates for a .gitignore
Then I’d like to do something like update editorconfig --t=gitignore_projectTypeA (Then the template gitignore_projectTypeA from ~\templates would be taken).

Is this something which is already possible resp. you are considering to implement?

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:10 (4 by maintainers)

Top GitHub Comments

2reactions

tunnckoCorecommented, Jul 20, 2016

I’m also for hidden place. I also seen that node-toolkit org recently.

But about the paths. For me it make best sense if it follow some convention like that ~/.node-toolkit/update/updater-name-or-generator-name/templates, because the structure of the repos are the same. But also seeing why ~/.node-toolkit/update/templates is good too.

1reaction

stefanwalthercommented, Jul 27, 2016

Yes, makes a lot of sense, thx for clarification.