slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update addons tests, note a todo

Browse Source
This commit is contained in:
Simon Michael 2017-03-29 08:21:30 -07:00
parent 8d1b1fbfc5
commit 7d0734f1ed
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
tests/addons/addons.test
View File

@ -1,19 +1,25 @@
# "make test" sets up the dummy add-on scripts required for these tests # "make test" sets up the dummy add-on scripts required for these tests
#XXX these don't obey shelltest -w, always running the hledger executable in PATH # Note because of the PATH setting these don't obey shelltest -w,
# they always run the first hledger executable in PATH
# 14. flags after an add-command are handled by the add-on # 1. flags after an add-command are handled by the add-on
PATH=$PATH:. hledger addon --help PATH=$PATH:. hledger addon --help
>>> /hledger-addon/ >>> /hledger-addon/
>>>=0 >>>=0
# 15. add-on flags which are not also defined in the main executable are a problem # 2. add-on flags which are not also defined in the main executable are a problem
PATH=$PATH:. hledger addon --addonflag PATH=$PATH:. hledger addon --addonflag
>>>2 /Unknown flag: --addonflag/ >>>2 /Unknown flag: --addonflag/
>>>=1 >>>=1
# 16. hledger main executable ignores anything after -- (and hides the -- from the add-on) # 3. hledger main executable ignores anything after -- (and hides the -- from the add-on)
PATH=$PATH:. hledger addon --help -- --addonflag PATH=$PATH:. hledger addon --help -- --addonflag
>>> /hledger-addon/ >>> /hledger-addon/
>>>=0 >>>=0
# TODO how to reliably ensure no addons but still find the hledger executable ?
# 4. having no addons shouldn't break the commands list
# PATH= ~/.local/bin/stack exec -- hledger
#>>>=0