refactor: remove <Plug> mapping surface #364

Merged

barrettruth merged 1 commit from fix/delete-plug-mappings into main

2026-04-20 14:32:23 +00:00

barrettruth commented

2026-04-20 14:32:12 +00:00

Problem

forge.nvim exposes a parallel mapping surface even though its real public interaction points are already :Forge and require('forge').open(). The plug mappings duplicate the route surface, add tests and help maintenance, and make the public API boundary less clear.

Solution

Remove the mappings entirely, delete their dedicated spec coverage, and trim the vimdoc to point users at :Forge and require('forge').open() as the interactive surface. Verified with nix develop /tmp/forge.nvim/delete-plug-mappings/#ci --command busted and nix develop /tmp/forge.nvim/delete-plug-mappings/#ci --command vimdoc-language-server check /tmp/forge.nvim/delete-plug-mappings/doc/.

## Problem forge.nvim exposes a parallel <Plug> mapping surface even though its real public interaction points are already `:Forge` and `require('forge').open()`. The plug mappings duplicate the route surface, add tests and help maintenance, and make the public API boundary less clear. ## Solution Remove the <Plug> mappings entirely, delete their dedicated spec coverage, and trim the vimdoc to point users at `:Forge` and `require('forge').open()` as the interactive surface. Verified with `nix develop /tmp/forge.nvim/delete-plug-mappings/#ci --command busted` and `nix develop /tmp/forge.nvim/delete-plug-mappings/#ci --command vimdoc-language-server check /tmp/forge.nvim/delete-plug-mappings/doc/`.