[Feature Request] Make hard-coded keymaps configurable via `setup()`

[vinicius507]

Greetings,

Currently the plugin uses hard-coded keymaps for code-preview.nvim actions (some of them are buffer local, like ]c and [c for navigating between changes), which makes it not that big of a deal. But <leader>dq for example is a global keymap and conflict with user's defined keymaps:

code-preview.nvim/lua/code-preview/init.lua

Lines 143 to 145 in 9ec3a33

	vim.keymap.set("n", "<leader>dq", function()
	require("code-preview.diff").close_diff_and_clear()
	end, { desc = "Close code-preview diff" })

It would be nice if we could configure the keymaps via setup() function or if you simply provided <Plug> keymaps so we could create the keymaps ourselves, even if outside of the plugin setup process.

Thanks in advance.

[Cannon07]

Hey @vinicius507, thanks for the well-scoped suggestion! This shipped in #44 and is now on main.
You can now configure all three previously-hardcoded keymaps via setup():

require("code-preview").setup({
  keys = {
    next_change = "]c",          -- inline diff: next change
    prev_change = "[c",          -- inline diff: previous change
    close_all   = "<leader>dq",  -- close diff and clear indicators
  },
})

I went with the keys table as the primary API since it's the convention most Neovim users expect, and added the mapping for the global close_all action since that was the one most likely to conflict. Let me know if you'd like mappings for the inline navigation actions too — closing this for now, but happy to reopen.