With the julia engine offering first-class support for Julia, we started running into issues of "engine priority": when two engines provide overlapping support, which should win? Currently the priority is hard-coded, which makes configuration awkward for projects that mostly use the julia engine.
An engines key in _quarto.yml could take an array of strings and control the resolution order. For example,
engines:
- julia
- jupyter
- knitr
This would allow the julia engine to take higher priority than jupyter in projects where that is the desired outcome. Because we have a default ordering, this wouldn't break backwards compatibility either.
mcanouil
commented
4 weeks ago
(cc @MichaelHatherly @jkrumbiegel)
With the
juliaengine offering first-class support for Julia, we started running into issues of "engine priority": when two engines provide overlapping support, which should win? Currently the priority is hard-coded, which makes configuration awkward for projects that mostly use thejuliaengine.An
engineskey in_quarto.ymlcould take an array of strings and control the resolution order. For example,This would allow the
juliaengine to take higher priority thanjupyterin projects where that is the desired outcome. Because we have a default ordering, this wouldn't break backwards compatibility either.