You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if it would be feasible to support ftplugin workflows.
Specifically, I'd like to be able to add adapters to neotest using files in, e.g.
ftplugin/haskell.lua
ftplugin/rust.lua
ftplugin/java.lua
etc.
At a first glance, it looks like, this could easily be achieved by changing
Taking this a step further, adapters could potentially self-register themselves in an ftplugin script, if the file that triggered the script to be sourced is a test file.
The caveat to the above approach is that vim.tbl_deep_extend doesn't merge lists,
so the user_config.adapters list would be overwritten.
This could be mitigated either by inserting into the existing table, or by providing a separate register_adapter API.
Hey 👋
I was wondering if it would be feasible to support
ftplugin
workflows.Specifically, I'd like to be able to add adapters to neotest using files in, e.g.
ftplugin/haskell.lua
ftplugin/rust.lua
ftplugin/java.lua
etc.
At a first glance, it looks like, this could easily be achieved by changing
neotest/lua/neotest/config/init.lua
Line 370 in 73043d6
to
Taking this a step further, adapters could potentially self-register themselves in an
ftplugin
script, if the file that triggered the script to be sourced is a test file.The caveat to the above approach is that
vim.tbl_deep_extend
doesn't merge lists,so the
user_config.adapters
list would be overwritten.This could be mitigated either by inserting into the existing table, or by providing a separate
register_adapter
API.@rcarriga what are your thoughts?
The text was updated successfully, but these errors were encountered: