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

;convert extant addon tests to shellrunner format 3

Browse Source
This commit is contained in:
Jacek Generowicz 2019-12-08 18:23:48 +01:00
parent 4593963fef
commit c6da152e9a
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
tests/addons/addons.test
View File

@ -4,24 +4,24 @@
# they always run the first hledger executable in PATH # they always run the first hledger executable in PATH
# 1. 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
# 2. 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
# 3. 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 ? # TODO how to reliably ensure no addons but still find the hledger executable ?
# 4. having no addons shouldn't break the commands list # 4. having no addons shouldn't break the commands list
# PATH= ~/.local/bin/stack exec -- hledger # $ PATH= ~/.local/bin/stack exec -- hledger
#>>>=0 # >=0
# ############################ issue 457 ##################################### # ############################ issue 457 #####################################
# # # #