The workaround for implementing the custom dotnet dap strategy prior to this is no longer required, so it can be simplified so the user just needs to follow the guidance from neotest core, instead of the hacky way neotest-dotnet is doing it at the moment.
Based on latest changes to neotest (https://github.com/nvim-neotest/neotest/discussions/24#discussioncomment-5784547) the
strategyparameter can now be a custom function.The workaround for implementing the custom dotnet dap strategy prior to this is no longer required, so it can be simplified so the user just needs to follow the guidance from
neotestcore, instead of the hacky way neotest-dotnet is doing it at the moment.