nvim-tree / nvim-tree/nvim-tree.lua
Investigate usefulness of healthcheck
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 8.6k
- Forks
- 639
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
- we could check for configuration issues - vim.notify could refer user to healthcheck for details
- we could check platform and notify (info) what functionalities are not supported
- We could check for mapping issues (?), say missing
trashcommand
Contributor guide
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.
Research direction
The issue names healthcheck, vim.notify, platform support, configuration checks, mapping issues, and the missing trash command, but no files or tests. Start by locating the existing healthcheck and notification behavior, then define which checks should be reported and how completion will be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100