marc/ale
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2024-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
ale/test/command_callback/test_elm_make_command_callback.vader

64 lines
2.6 KiB
Text
Raw Normal View History

Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
Before:
call ale#assert#SetUpLinterTest('elm', 'make')
After:
unlet! g:executable
call ale#assert#TearDownLinterTest()
Execute(should get valid executable with default params):
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
call ale#test#SetFilename('../elm-test-files/newapp/src/Main.elm')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
let g:executable = ale#path#Simplify(g:dir . '/../elm-test-files/newapp/node_modules/.bin/elm')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
AssertLinterCwd ale#path#Simplify(g:dir . '/../elm-test-files/newapp')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
AssertLinter g:executable,
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
\ ale#Escape(g:executable) . ' make --report=json --output=/dev/null %t'
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
Execute(should get elm-test executable for test code with elm >= 0.19):
call ale#test#SetFilename('../elm-test-files/newapp/tests/TestSuite.elm')
let g:executable = ale#path#Simplify(g:dir . '/../elm-test-files/newapp/node_modules/.bin/elm-test')
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
AssertLinterCwd ale#path#Simplify(g:dir . '/../elm-test-files/newapp')
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
AssertLinter g:executable,
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
\ ale#Escape(g:executable) . ' make --report=json --output=/dev/null --compiler '
Pass --compiler flag to elm-test when linting 0.19 tests This makes elm make linter work when elm is not installed globally.
2019-01-19 21:04:41 +00:00
\ . ale#path#Simplify(g:dir . '/../elm-test-files/newapp/node_modules/.bin/elm') . ' %t'
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
fallback to elm if elm-tests isn’t available
2019-01-04 06:57:14 +00:00
Execute(should fallback to elm executable with elm >= 0.19):
call ale#test#SetFilename('../elm-test-files/newapp-notests/tests/TestMain.elm')
let g:executable = ale#path#Simplify(g:dir . '/../elm-test-files/newapp-notests/node_modules/.bin/elm')
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
AssertLinterCwd ale#path#Simplify(g:dir . '/../elm-test-files/newapp-notests')
fallback to elm if elm-tests isn’t available
2019-01-04 06:57:14 +00:00
AssertLinter g:executable,
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
\ ale#Escape(g:executable) . ' make --report=json --output=/dev/null %t'
fallback to elm if elm-tests isn’t available
2019-01-04 06:57:14 +00:00
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
Execute(should get plain elm executable for test code with elm < 0.19):
call ale#test#SetFilename('../elm-test-files/oldapp/tests/TestSuite.elm')
let g:executable = ale#path#Simplify(g:dir . '/../elm-test-files/oldapp/node_modules/.bin/elm')
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
AssertLinterCwd ale#path#Simplify(g:dir . '/../elm-test-files/oldapp')
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
AssertLinter g:executable,
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
\ ale#Escape(g:executable) . ' make --report=json --output=/dev/null %t'
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
Execute(should get valid executable with 'use_global' params):
let g:ale_elm_make_use_global = 1
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
call ale#test#SetFilename('../elm-test-files/newapp/src/Main.elm')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
AssertLinterCwd ale#path#Simplify(g:dir . '/../elm-test-files/newapp')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
AssertLinter 'elm',
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
\ ale#Escape('elm') . ' make --report=json --output=/dev/null %t'
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
Execute(should get valid executable with 'use_global' and 'executable' params):
let g:ale_elm_make_executable = 'other-elm'
let g:ale_elm_make_use_global = 1
support tests/ with elm 0.19.0 With earlier elm versions, a separate package file is maintained for tests, which when properly configured enabled the compiler to find what it needed to compile the tests. Under elm 0.19, test dependencies are managed in the top-level package file, so `elm make` will fail on the tests. `elm-test make` is required in this case. See https://github.com/elm-explorations/test/issues/64
2019-01-01 18:42:06 +00:00
call ale#test#SetFilename('../elm-test-files/newapp/src/Main.elm')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
AssertLinterCwd ale#path#Simplify(g:dir . '/../elm-test-files/newapp')
Simplify the code for most linters and tests with closures
2018-08-02 22:44:12 +00:00
AssertLinter 'other-elm',
Close #2281 - Separate cwd commands from commands Working directories are now set seperately from the commands so they can later be swapped out when running linters over projects is supported, and also better support filename mapping for running linters on other machines in future.
2021-03-01 20:11:10 +00:00
\ ale#Escape('other-elm') . ' make --report=json --output=/dev/null %t'
Reference in a new issue Copy permalink