prefix module options

[Alexnortung]

Hello, I think it would make sense to prefix module options with something like Neve., just so it won't conflict with other modules.

So instead of bufferline.enable it would be Neve.bufferline.enable.

[jee-mj]

Hello, I think it would make sense to prefix module options with something like Neve., just so it won't conflict with other modules.

So instead of bufferline.enable it would be Neve.bufferline.enable.

These options come from NixVim. Neve is essentially a configuration of NixVim.

As I understand, resolving this issue would require forking NixVim and using that fork of NixVim as an input. NixVim already follows the syntax you are suggesting:

(programs.)nixvim.plugins.bufferline.enable

Hence, I believe that you might be confusing what Neve accomplishes. Always a chance I'm wrong though, so if you have any examples of where Neve causes conflicts (regardless of whether they exist in NixVim), please share ^_^

[Alexnortung]

Hello, the options I am referring to are the ones defined in the Neve modules.
I am aware that it does not conflict with anything in Nixvim, however with the current naming of the modules, I cannot make my own module called bufferline. For an example I think it would be nice if I could make my own bufferline module and then enable that module would set Neve.bufferline.enable = true, so that my module in a sense extends the Neve bufferline module.