Closed catgoose closed 4 months ago
I see this is because of https://github.com/thenbe/neotest-playwright/issues/20
Would it be possible to add a config option with project name as key to define the playwright projects since vim.ui.select
wrappers don't allow selecting properly?
Harcoding the project names would get messy when using this plugin on multiple projects. Instead, I've added an experimental telescope picker in #31 that attempts to solve this.
The issue here occurs if:
NeotestPlaywrightProject
playwright.config.ts
Since they were removed from playwright.config.ts
, they are unavailable for deselection. I guess they are still "active" in whatever state file neotest-playwright
uses to save the projects.
You have to add the projects back to the config then deselect them again. Then it is safe to remove them using NeotestPlaywrightProject
Ah yes.
p.s. You can run this command to see where the file is stored. Then you can delete it if you encounter lingering phantom projects.
:lua =vim.fn.stdpath('data') .. '/neotest-playwright.json'`
See e35465a43729dbf9f790c56c9c6e3402ba27a2c0 for how to quickly recover from phantom project issue.
Using Neovim 0.10.
If I use a playwright config without
firefox
orwebkit
, running tests complains about those projects not being found.I select 'chromium' using NeotestPlaywrightProject then try to run playwright tests:
My lazy.nvim config:
playwright config: