Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(extension): Fix extension configuration for which-key.nvim extension #405

Merged
merged 2 commits into from
Oct 11, 2023

Conversation

mrjones2014
Copy link
Owner

Resolves: #404

How to Test

  1. Which-key.nvim integration should work

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 mrjones2014 merged commit 8aa92c5 into master Oct 11, 2023
2 checks passed
@mrjones2014 mrjones2014 deleted the mrj/404/fix-whichkey-extension branch October 11, 2023 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: which_key config issue - attempt to index field 'which_key' (a nil value)
1 participant