locochris
locochris
:+1:
@eileencodes as @toxaq mentioned - its a formatting issue and there's a failing test case in the PR. It saves us (and probably @nicolasblanco , @toxaq et al) from having...
no worries - how's it look now @eileencodes ? BTW its whitespace in the _output_ not in the _input_ (if there was any confusion there). ie. it was a poorly...
@futuretap - confirmed using a freshly created `global_phone.json` (even with the whitespace fix of #9). I've never tried to understand how the json is being generated, but perhaps there's some...
ie. same behaviour as many other tools eg `sed` - read from file (if specified) or STDIN (if not).
What about passing them back to the parent using a fifo? ``` bash [ -e /tmp/shpec.fifo ] || mkfifo /tmp/shpec.fifo time for file in $files; do (. "$file"; echo $failures...
That way the tests can still output to stdout (something I'm relying on in [syscheck](https://github.com/locochris/syscheck) a system checker that wraps shpec) _and_ communicate success and failure.
What about `xit` instead of `pending it`? (ie. similar to https://www.relishapp.com/rspec/rspec-core/v/2-0/docs/pending/pending-examples#temporarily-pending-by-changing-"it"-to-"xit")