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.

Remove required argument from the template command

See original GitHub issue

Is your feature request related to a problem? Please describe.

Running perla templates without arguments should show the table of the current templates available for perla’s scaffolding features, but currently it requires an argument (namely the template name for the rest of the operations related to templates)

Describe the solution you’d like We should make the required templateName optional, and just default to show the list of existing templates available for perla.

In regards of the information of the table it currently displays the following columns:

Name
Group
Belongs To
Parent Location
Last Update

Taking feedback from #118 I’m considering using the following columns instead:

Name
perla new <project> -t
perla new <project> -id
perla new <project> -tn

e.g.

Name	perla new <project> -t	perla new <project> -id	perla new <project> -tn
Fable Feliz	perla new -t ff	perla new -id perla.templates.fable.feliz	perla new -tn AngelMunoz/perla-templates/fable-feliz
Fable Sutil	perla new -t fs	perla new -id perla.templates.fable.sutil	perla new -tn perla-templates/fable-sutil

One potential issue here is that -tn can be provided partially or fully annotated. The shorthand form (no GH user) in the example it works because there is a single repository with the perla-templates name, the following wouldn’t work and you will need to provide the full name:

AngelMunoz/perla-templates
fable-compiler/perla-templates

So we could remove that option completely at least for users

Describe alternatives you’ve considered A Wizard-like experience for templates as well, perla template runs a wizard-like experience just as perla new does