Consider writing rebar3 templates and shipping them with LFE

[yurrriq]

If you put rebar3 templates in priv/ at the project root, they're usable in projects that depend on them.

I think it'd be cool to be able to do:

$ rebar3 new lfe sup
$ rebar3 new lfe gen_server
$ rebar3 new lfe unit-test

etc

[oubiwann]

Here are my thoughts:

• basic library template -- cool
• OTP templates (for gen_server, get_event, gen_fsm, etc.) -- cool
• templates that require any other library in order to be useful -- I'd vote for those going in their respective library's priv dirs ...

Regardless, this capability of rebar3 is neat; I didn't know that it would take advantage of the deps libs priv dirs for templates.

[yurrriq]

Agreed. For templates packaged with the language, I was thinking just barebones stuff like OTP behaviours and maybe super generic application and library templates.

[rvirding]

Now I have to expose my ignorance here. Why would I need a template for
gen_server etc? And what is in such a template?

Robert

On 21 March 2016 at 07:26, Eric Bailey notifications@github.com wrote:

Agreed. For templates packaged with the language, I was thinking just
barebones stuff like OTP behaviours and maybe super generic application and
library templates.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#203 (comment)

[oubiwann]

These templates are shipped with rebar3_lfe:

• https://github.com/lfe-rebar3/rebar3_lfe/tree/release/0.3.x/priv/templates

Documented here:

• https://lfe.io/reference/lfe-rebar3/current/command-ref/projects/index.html

Closing ...