plugin-template.nvim
vusted
plugin-template.nvim | vusted | |
---|---|---|
6 | 5 | |
104 | 72 | |
- | - | |
0.0 | 5.7 | |
5 months ago | 3 months ago | |
Lua | Lua | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
plugin-template.nvim
-
Arduino.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
-
Some questions about Lua plugin development
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
-
What are good general guidelines/tips for someone writing a plugin in Lua?
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?
-
Help with a Lua plugin
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
- A template for plugins written mostly in Lua
-
How do you build unit tests for your lua plugins?
I had the same trouble recently so I put together a template with the solution I found: https://github.com/m00qek/plugin-template.nvim
vusted
-
How to write `pretty_print`ed json data into a json file?
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.
-
🌿 nvim-laurel: Another set of syntax sugar macros in Fennel
nvim-laurel provides syntax sugar macros for Neovim. The macros are developed with fennel-language-server, and tested with vusted.
-
GitHub - hkupty/runes.nvim: Lua test framework for neovim plugins
How does it compare to [vusted](https://github.com/notomo/vusted) or [plenery test](https://github.com/nvim-lua/plenary.nvim#plenarytest_harness) ?
-
Simple examples of neovim integration tests?
Checkout vusted as alternative to plenary.
-
How do you build unit tests for your lua plugins?
Also came across vusted the other day. Haven't yet tried it though :)
What are some alternatives?
nvim-comment - A comment toggler for Neovim, written in Lua
plenary.nvim - plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.
baleia.nvim - Colorize text with ANSI escape sequences (8, 16, 256 or TrueColor)
nvim-luapad - Interactive real time neovim scratchpad for embedded lua engine - type and watch!
boilit - create boilerplate structure for neovim plugins
snippet-converter.nvim - Bundle snippets from multiple sources and convert them to your format of choice.
package-info.nvim - ✍️ All the npm/yarn/pnpm commands I don't want to type
orgmode - Orgmode clone written in Lua for Neovim 0.9+.
vim-lsp - async language server protocol plugin for vim and neovim
fennel-language-server - Fennel language server protocol (LSP) support.