diff options
author | Fred Hebert <mononcqc@ferd.ca> | 2015-12-18 22:44:20 -0500 |
---|---|---|
committer | Fred Hebert <mononcqc@ferd.ca> | 2015-12-19 20:16:49 -0500 |
commit | 44a30ca52f3c74d19007fd0433f6192fa4ccca79 (patch) | |
tree | 12e5be5a54ff9d3bcb692bad3800505f2abe7bae /test/rebar_unlock_SUITE_data/rebar.lock | |
parent | ddc64cd66b2d6e4e2315ee281b9eabb8bc2e8868 (diff) |
Plugin templates enabled
This lets a plugin define templates to be loaded:
$ rebar3 new
...
proper (plugin): A basic PropEr suite for an OTP application
...
$ rebar3 new help proper
proper:
plugin template (...)
Description: A basic PropEr suite for an OTP application
Variables:
name="suite" (...)
...
→ rebar3 new proper fakesuite
===> Writing test/prop_fakesuite.erl
In this case, proper is a fake template file I've put by hand in
_build/default/plugins/rebar3_proper/priv/<somename>/, meaning it will
only work as far as it's called from the project's root.
The priority order of plugins is now .config > plugin > built-in, such
that someone could ensure plugins do not crush their own private
templates, but also that custom or plugin templates do overtake built-in
ones. It used to be Built-in > .config only.
Templates are searched for recursively in the priv/ directory of
plugins.
Diffstat (limited to 'test/rebar_unlock_SUITE_data/rebar.lock')
0 files changed, 0 insertions, 0 deletions