Suggestion: extend accessibility by improving mapping config
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.6k
- Forks
- 357
- Avg merge
- 15h 47m
- Merged PRs (30d)
- 2
Description
Instead of:
finder = {
["<cr>"] = "Select",
["<c-c>"] = "Close",
...
}
finder = {
select = { "<cr>" },
close = { "<c-c>" },
...
}
Allowing to set multiple mappings per action.
A change like this could be added as addition to the current config with a deprecation notice for the current values, the notice should turn into a warning after some weeks before the old config is removed.
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 locating the Lua finder mapping configuration and its existing parsing or validation tests. Confirm how the current action-to-key format is handled, then define completion as supporting multiple mappings per action while preserving the old format through the proposed deprecation and warning stages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, neovim
- Domain
- accessibility, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100