Nested file structure in specified plugins folder

[dasupradyumna]

Hello everyone!
I have been using the manager to maintain a plugins directory, which contains all the plugin spec files so far.
But as the number of plugins keep increasing, I want to organize related plugin specs into subfolders.
For example, as most users know, having a fully functional LSP environment in NeoVim requires quite a few plugins like mason, nvim-lspconfig, nvim-cmp (and sources), etc.
If possible, I would like it so that the setup (plugin specs) directory is recursively searched for plugin configs, instead of only the top level like it is currently. Or does anyone have a clean workaround for this kind of organization?

Does this belong in discussions or should I open a feature request for this?

Cheers~

[folke]

I'm not planning to add recursive loading to lazy.

You can achieve something similar by using import.

So add this to your specs:

return {
  {import = "plugins.lsp" }
}

That will import all the specs under lua/plugins/lsp

Make sure lua/plugins/lsp/init.lua or lua/plugins/lsp.lua does not exist, or they will be loaded twice

[dasupradyumna]

That's a clean solution!
Thanks Folke! :)