feat(quarto): dynamically set codeRunner.default_method based on avai… - #1595
feat(quarto): dynamically set codeRunner.default_method based on avai…#1595iamralch wants to merge 2 commits into
Conversation
…lable dependencies Detects presence of "iron.core" and "molten.health" modules at runtime and sets `codeRunner.default_method` accordingly in the quarto-nvim plugin options.
Review ChecklistDoes this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist: Proper conventional commit scoping:
|
|
Hey. What about |
|
@azdanov slime is the default option. Do you want me to set it explicitly? |
|
Nope, probably not needed if it's default. Just asking since I don't know anything about this plugin apart from reading docs. Can there be a situation where a user has both iron and molten installed simultaneously? |
|
I haven't used them in one configuration. I suspect that they are compatible. The difference is that molten is handling jupyter notebooks vs iron is a repl for python and other languages. |
|
@Uzaaft Do you have any experience with these? I'm only certain of web dev stuff, this looks like data science. |
Uzaaft
left a comment
There was a problem hiding this comment.
Not sure I like how one plugin is prioritized over the other, but the community will provide feedback.
Actually I think this is the wrong way to go around it.
|
After a second lookover, I feel like this code smells too much. |
Detects presence of "iron.core" and "molten.health" modules at runtime and sets
codeRunner.default_methodaccordingly in the quarto-nvim plugin options.