summaryrefslogtreecommitdiff
path: root/test/test_elm_executable_detection.vader
diff options
context:
space:
mode:
authorKeith Pinson <kazark@zoho.com>2017-10-06 17:26:50 -0400
committerKeith Pinson <kazark@zoho.com>2017-10-06 17:26:50 -0400
commitf21f52343db942bd39ed6a2bb196d01aaf1f741f (patch)
tree7a5770a570657a321087c0dcc7f8d0d0d524d0e9 /test/test_elm_executable_detection.vader
parent47577564a2294668d7997b261e17fd97f0dd1fe6 (diff)
downloadale-f21f52343db942bd39ed6a2bb196d01aaf1f741f.zip
Fix Elm linter for Windows (resolves #980)
Looks like elm-make only respects /dev/null, even on Windows. The person who wrote this linter maybe did not test it on Windows, and wrote the code in the way you would expect to be solid by using NUL on Windows. However it seems elm-make is not actually making use of /dev/null but rather using it as a form of flag. Ironically this seems to be what is already described in the comments; I added some clarification.
Diffstat (limited to 'test/test_elm_executable_detection.vader')
0 files changed, 0 insertions, 0 deletions