Make markdown vale linter command configurable with options (#3594)

* Make vale command user-configurable

* Add test for vale options

* Typo in test

Co-authored-by: David Balatero <dbalatero@stripe.com>
This commit is contained in:
David Balatero
2021-02-17 20:10:49 -05:00
committed by GitHub
parent 88d052b5a9
commit 0b35c3a5b9
2 changed files with 49 additions and 2 deletions

View File

@@ -0,0 +1,32 @@
Before:
call ale#assert#SetUpLinterTest('markdown', 'vale')
call ale#test#SetFilename('dummy.md')
let g:ale_markdown_vale_executable = 'vale'
let g:ale_markdown_vale_input_file = '%t'
let g:ale_markdown_vale_options = ''
After:
call ale#assert#TearDownLinterTest()
Execute(Executable should default to vale):
AssertLinter 'vale', ale#Escape('vale')
\ . ' --output=JSON %t'
Execute(Should be able to set a custom executable):
let g:ale_markdown_vale_executable = 'bin/vale'
AssertLinter 'bin/vale' , ale#Escape('bin/vale')
\ . ' --output=JSON %t'
Execute(Should be able to set custom options):
let g:ale_markdown_vale_options = '--foo --bar'
AssertLinter 'vale', ale#Escape('vale')
\ . ' --output=JSON --foo --bar %t'
Execute(Should be able to set a custom input file):
let g:ale_markdown_vale_input_file = '%s'
AssertLinter 'vale', ale#Escape('vale')
\ . ' --output=JSON %s'