nvim-flutter / nvim-flutter/flutter-tools.nvim
Migrate all UI elements to use Nui.nvim
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 1.4k
- Forks
- 116
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Using a UI framework like nui.nvim will reduce the maintenance burden of this plugin since as well as managing the LSP and finding executables we wouldn't also have to maintain a mini UI library as well and could just depend on another tool for that. nui has become quite mature and is depended on by a lot of other plugins so would hopefully end up being something a user has installed anyway, as well as all that it would allow me to simplify the functionality and responsibilities of this plugin greatly
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
Start by inspecting the plugin's existing UI elements and the nui.nvim documentation linked in the issue. Identify every UI surface that would need migration and define completion as all UI elements using nui.nvim while preserving the plugin's current responsibilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100