Specs in subdirectories

[bennypowers]

Can I arrange my plugins in subdirs, like

plugins/init.lua
plugins/editing/caser.lua
plugins/editing/motion.lua
plugins/lsp/mason.lua

Will require'lazy'.setup'plugins' get all of those by default?

[folke]

Only top-level and first level plugin specs are automatically loaded, but you can use import to import other directories and sub-directories.

As your spec, you can use:

{
  {import = "plugins"},
  {import = "plugins.editor"},
}

This is currently not yet documented. Will do so in a bit.

[bennypowers]

Nice! That's perfect https://github.com/bennypowers/dotfiles/blob/cca747c27d400133dcce9cdce70ed6ab9d0980c1/.config/nvim/lua/plugins/init.lua

[runiq]

Quick followup question from the peanut gallery—the import directive is what enables the lazy-loading functionality, right?

What I mean is, if I did this:

-- as my spec
{
  {import = "plugins"},
}

-- in plugins.lua
require("plugins.editor")

…then plugins.editor would only be lazy-loaded if something required plugins. But if I did this:

{
  {import = "plugins"},
  {import = "plugins.editor"},
}

…then lazy loading would work for both modules, no?

[folke]

import is not related to lazy-loading. It just imports other specs into the spec where you do the import.

It's better to use import instead of requiring yourself, to make things like change detection work properly.

[runiq]

Gotcha, thanks!

[runiq]

Sorry, another question: Does {import = "plugins.editor"} also import one level of submodules, e.g. plugins.editor.caser and plugins.editor.motion in OP's case?

Edit—think I answered my own question: The Readme claims that this should be the case.