mattpolzin / mattpolzin/dev-env
Explore trouble.nvim
Open
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Consider using https://github.com/folke/trouble.nvim if it can offer a whole-project view of diagnostic warnings.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by reviewing the dev-env configuration and trouble.nvim's documented diagnostic features, then determine whether it can provide a whole-project warning view. Done means reaching and recording a clear conclusion about its suitability, with any resulting integration scope identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100