spec = {{ import = "plugins" }} when plugins contains submodules loads all plugins, including those from submodules. Is this a lazy thing, nvim thing, or lua thing?

[Gremious]

I have the following simple setup for lazy.nvim:

plugin_manager.lua contains

require("lazy").setup({
	spec = {{ import = "plugins" }},
})

where plugins is a folder with an init.lua. It itself just has a regular return of a plugin spec, e.g. nothing more than:

return { "michaelb/do-nothing.vim", ... }

Under said plugins module folder, have other .lua files with more simple spec returns, as well as a folder submodule: /text/init.lua which also has a /text/treesitter.lua under it.

What surprised me is this:

When I did spec = {{ import = "plugins" }} it loaded every plugin from the plugins module, up to text/init.lua but excluding text/treesitter.lua. I expected I would have needed to add a spec for basically every lua file, e.g.

require("lazy").setup({
	spec = {
		{ import = "plugins" },
		{ import = "plugins.themes" },
		{ import = "plugins.text" },
		{ import = "plugins.text.treesitter" },
		...	
	},
})

but it seems I only need { import = "plugins" }, { import = "plugins.text" }

(and I am personally quite happy about that, to be fair, less lines to maintain - though it does make it confusing as to what the load order is)

My question is, is this:

1. The way that lazy.nvim is programmed to work
2. A quirk of nvim's init.lua and maybe it combines returns or something?
3. The way that lua modules works? (I tried in repl and require-ing a module didn't seem to nest their returns or anything, so probably not)

[Gremious]

Found my answer in the docs, finally:

Info: https://lazy.folke.io/usage/structuring

The specs from the module and any top-level sub-modules will be merged together in the final spec, so it is not needed to add require calls in your main plugin file to the other files.

Example: https://lazy.folke.io/installation