Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom test function names are not handled #65

Open
nicos68 opened this issue Feb 3, 2024 · 2 comments · May be fixed by #66
Open

Custom test function names are not handled #65

nicos68 opened this issue Feb 3, 2024 · 2 comments · May be fixed by #66

Comments

@nicos68
Copy link

nicos68 commented Feb 3, 2024

I am working on a project for which we have cutomized the python_functions option value (using the pyproject.toml file). In this case neotest-python does not detect the tests.

I tried fiddling with the treesitter query and it does solve the issue.

@nicos68 nicos68 linked a pull request Feb 11, 2024 that will close this issue
@alecgerona
Copy link

Do you have an existing workaround while this is still being looked at? I don't know how to request a bump for your pr.

@nicos68
Copy link
Author

nicos68 commented May 27, 2024

There are two things you can do

  • Since this repo hasn't had any update since my pr, you can just point your plugin manager to my PR branch on my fork, as long as the repo is not updated you won't miss any new feature
  • Modify the treesitter query on your local copy of the plugin's lua code. That's what I have done at work. Personally I still use packer, so the file is located at ~/.local/share/nvim/site/pack/packer/start/neotest-python/lua/neotest-python/base.lua

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants