@kevintraver

Couldn't we just do the following

return {
  {
    "echasnovski/mini.pairs",
    keys = {
      {
        "<leader>up",
        function()
          local Util = require("lazy.core.util")
          vim.g.minipairs_disable = not vim.g.minipairs_disable
          if not vim.g.minipairs_disable then
            Util.info("Enabled auto pairs", { title = "Option" })
          else
            Util.warn("Disabled auto pairs", { title = "Option" })
          end
        end,
        desc = "Toggle mini.pairs",
      },
    },
  },
}

Why introduce new code of other plugins in lazyvim.util? This way the change will be entirely dependent on the plugin itself.

@kevintraver

Couldn't we just do the following

return {
  {
    "echasnovski/mini.pairs",
    keys = {
      {
        "<leader>up",
        function()
          local Util = require("lazy.core.util")
          vim.g.minipairs_disable = not vim.g.minipairs_disable
          if not vim.g.minipairs_disable then
            Util.info("Enabled auto pairs", { title = "Option" })
          else
            Util.warn("Disabled auto pairs", { title = "Option" })
          end
        end,
        desc = "Toggle mini.pairs",
      },
    },
  },
}

Why introduce new code of other plugins in lazyvim.util? This way the change will be entirely dependent on the plugin itself.

This is pretty much what I was thinking of too. The mapping and function can all be part of the plugin spec.

Ok, I updated the keymap to be in the spec. I also switched the enabled/disabled logic and remove the not to make the logic more clear.

thansk!