Closed dhruvmanila closed 2 years ago
Some test runners can take configuration via environment variables as well. For example, vusted can take VUSTED_NVIM and VUSTED_ARGS.
vusted
VUSTED_NVIM
VUSTED_ARGS
We can pass those variables in the cmd field like so:
cmd
{ cmd = "VUSTED_ARGS='--headless --clean' vusted" }
But I think it would be better to provide native support like so:
{ env = { VUSTED_ARGS = '--headless --clean', }, cmd = 'vusted', }
Internally, the env field will be converted to key=value string pairs and prefixed to the cmd field.
env
key=value
This is just a thought, it's ok if rejected :)
@dhruvmanila it's kinda easy to implement. Done for v0.6.0
you may setup it for a test runner:
require('nvim-test.runners.vusted'):setup { env = { VUSTED_ARGS = "--headless --clean" } }
Some test runners can take configuration via environment variables as well. For example,
vusted
can takeVUSTED_NVIM
andVUSTED_ARGS
.We can pass those variables in the
cmd
field like so:But I think it would be better to provide native support like so:
Internally, the
env
field will be converted tokey=value
string pairs and prefixed to thecmd
field.This is just a thought, it's ok if rejected :)