nvim-flutter / nvim-flutter/flutter-tools.nvim
[Feature Request] More Feedback for Slow Operations
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 1.4k
- Forks
- 116
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
For actions like hot reload or restart, or even building , launching the app, its a bit difficult to know if its actually doing anything, and if u glance away at the wrong time, u might not know that its finished.
Would it be possible to hook into whatever it is the lsp is using to notify for long standing tasks (ill attach screenshots of what I mean below, but its basically the little messages u see in the bottom right as its analyzing the code).
Alternatively, if we had events, that would enable people to choose what they want to happen themselves when these events occur.
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
Begin at the hot reload, restart, build, and launch entry points in the plugin and inspect how its LSP interactions report long-running work. Define whether the feature should expose progress messages, user-configurable events, or both; done requires a consistent completion signal for those operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, lua, neovim
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100