nvim-mini / nvim-mini/mini.nvim
Allow customization of mini.starter query
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 9.5k
- Forks
- 310
- Avg merge
- 4h 16m
- Merged PRs (30d)
- 1
Description
Contributing guidelines
- I have read CONTRIBUTING.md
- I have read CODE_OF_CONDUCT.md
Module(s)
mini.starter
Description
Mini.starter intentionally doesn't support fuzzy finding. However, allowing users to provide an "is item active" function would allow users to modify the query process themselves to add fuzzy-like functionality without impacting the design of starter. Is this a feature that might be considered?
A simple implementation would just be to allow starter's config to accept an is_item_active property that, when set, would override H.is_item_active.
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 reading the mini.starter module and its current H.is_item_active query path. Determine how a configurable is_item_active function should interact with the existing default behavior, then verify that custom callbacks can change item activation without affecting users who leave the option unset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100