let which-key handle key binding if which-key integration is used

[mrjones2014]

Resolves: #[issue number]

How to Test

1. Please leave detailed testing instructions

Testing for Regressions

I have tested the following:

• Triggering keymaps from legendary.nvim in all modes (normal, insert, visual)
• Creating keymaps via legendary.nvim, then triggering via the keymap in all modes (normal, insert, visual)
• Triggering commands from legendary.nvim in all modes (normal, insert, visual)
• Creating commands via legendary.nvim, then running the command manually from the command line
• augroup/autocmds created through legendary.nvim work correctly

[mrjones2014]

@bennypowers you use which-key right? Would you mind testing this out?

Original purpose was for something else but I think it’s a good improvement regardless. Removes some redundant mapping.

[bennypowers]

how would this affect my config?

[mrjones2014]

You shouldn't need to change anything, I think I'm just doing unnecessary work, so as long as nothing breaks for you testing this branch, it should be all good.

[bennypowers]

I poked around for a few minutes and both legendary menu and which-key bindings seem to work fine

[mrjones2014]

Thanks for testing! I’ll get this merged soon then.

[mrjones2014]

@bennypowers I made a few changes, can you test one more time?

[bennypowers]

yeah looks ok. I didn't do exhaustive testing, but I did confirm that at least one or two of the bindings that I set up in my which-key config file appeared in both places

[mrjones2014]

Awesome, that's all that this PR should really affect. Going to merge. Thanks!