[Feature] Add variable indicator when running tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- lua
- Domain
- testing-qa
Research direction
Start with the init.lua example and trace how the nvim instance is launched for busted tests. Check how messages reach the test result window and determine where a variable such as vim.g.plenary_busted_test would be set. Done means init.lua can detect test execution and unrelated errors do not add extra output to the test result.
Written by the indexing model from the issue text.
Description
Adding something like vim.g.plenary_busted_test to indicate the nvim instance is running busted test would be helpful for managing init.lua conditionally, something not related to testing might error and print extra message on test result window which I don't want.
For example, I have a vim.cmd.colo 'xamabah' in my init.lua, it always errors
- Dominant language
- Lua
- Stars
- 3.5k
- Forks
- 340
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nvim-lua/plenary.nvim
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
nvim-lua/plenary.nvim#682 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nvim-lua/plenary.nvim#680 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nvim-lua/plenary.nvim#675 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
nvim-lua/plenary.nvim#672 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nvim-lua/plenary.nvim#671 · 1 comment ·
All issues in nvim-lua/plenary.nvim
Similar issues
-
Unconfirmed bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
luanti-org/luanti#17605 · 1 comment ·
Maintainers usually reply within 2 days
-
agent-in-progress agent-research-recommend enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
codymikol/multiverse.nvim#337 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nickjvandyke/opencode.nvim#336 ·
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
coder/claudecode.nvim#321 ·