plenary.nvim VS plugin-template.nvim

we can create a function to open a pop up menu using plenary.popup like this, you need to install neovim plenary if you don't already have it https://github.com/nvim-lua/plenary.nvim

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

I feel this :( That said, alot of plugins rely on plenary.nvim. Its up to you if you determine this is "non-essential" or not. It will almost certainly be available for you to use already.

The big reason I ask is that reaching out to an external python shell to run commands (disregard the fact that its python running) is going to be much slower than using the in built lua JIT interpreter. Additionally, plenary has a built in curl function so you don't have to "reinvent the wheel".

There is also test harness in nvim-lua/plenary.nvim with a slightly different design, but still usable of course.

I am simply using busted or more specifically vusted which is a wrapper around busted for Neovim. It should be quite straightforward to learn the basics, I would say you mostly need to know these functions: describe, it (these are used to structure your test cases) and assert.are_same (to check for table equality). Some people are also using plenary which is also based on busted.

It's based on nvim-lua-plugin-template, but uses Nix flakes to run plenary.nvim tests.

Plenary plugin for Nvim

I was put off by the complexity of adding tests but in the add I got it setup in my plugin by downloading a plugin template and copying the way everything is done. Probably this one https://github.com/m00qek/plugin-template.nvim

Hey, I have put together a template for Neovim plugins that proposes a structure and have a good setup for tests. Take a look, it might inspire you https://github.com/m00qek/plugin-template.nvim

Hello everyone, I created a plugin template for Neovim before and now I'm planning to add a general guidelines section to its documentation. To not make this too personal I'd like to hear from you what are good tips, guidelines, do/don't, etc. when writing a Lua plugin. Does anyone here have strong opinions on this?

I suggest you to add some tests to it, which will ensure that it keeps working when you add more stuff to if in the future. One way is to do setup them like in https://github.com/m00qek/plugin-template.nvim

I had the same trouble recently so I put together a template with the solution I found: https://github.com/m00qek/plugin-template.nvim