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 lazy.nvim extension from breaking change upstream #409

Merged
merged 1 commit into from
Oct 17, 2023

Conversation

mrjones2014
Copy link
Owner

Resolves: #408

How to Test

  1. Lazy.nvim extension should load keymaps from plugin specs

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 bf39c4a into master Oct 17, 2023
2 checks passed
@mrjones2014 mrjones2014 deleted the mrj/408/fix-lazy-extension branch October 17, 2023 11:36
for _, plugin in pairs(LazyNvimConfig.plugins) do
local keys = Handler.handlers.keys:values(plugin)
local keys = Handler.handlers.keys:_values(Plugin.values(plugin, 'keys', true), plugin)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to use the below instead:

local keys = plugin._.handlers.keys or {}

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]: Latest lazy.nvim update throws error
2 participants