vim-blueplanet
vim-ultest
vim-blueplanet | vim-ultest | |
---|---|---|
2 | 13 | |
10 | 380 | |
- | - | |
9.2 | 0.0 | |
about 2 months ago | over 1 year ago | |
Lua | Python | |
- | 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.
vim-blueplanet
-
FAVOURITE PLUGINS
To my knowledge vim-test has no out-of-the-box configuration for TypeScript. I forgot why. Anyway here is my configuration that adds mocha and jest as testers for TypeScript. Though it is mostly based on the existing JavaScript support of vim-test it adds some extra support for Vue testing and project local binaries. Finally ensure you enabled these testers in the vim-test configuration (g:test#custom_runners).
-
Do you use a single init.lua/.vim file or an organized directory structure? Just curious :)
You could take a look here at my configuration. Not sure if that is helpful. You should first read up native packages as it has been linked above. I don't explain the little sneaks and features here. But in its core I put file and directory structure above everything else. I barely import anything manually but fully rely on automated mechanisms. I use lazy loading heavily. I use a mix of .vim and .lua files depending on its content and which language is easier (e.g. mappings are simpler in VimL. In result I have hundreds of files in my configuration. My everything follows a structure. With tools like fzf or telescope it is too easy to open the file you search for. It's basically no overhead. It would be more work to find what I search for if I would have less files. Finally this keeps everything incredibly independent. I can add, change and especially remove thing very easily as most things are very separated and independent. I want to remove a plugin, all its config, mappings, highlights, signs, ... I just remove one directory. Nothing more and nothing less. Clean cut. If I want a plugin and everything around it (copy-paste from above) to be lazy loaded it just works out-of-the-box. It's very simple and elegant. In my opinion. Though you can easily dislike it if you don't agree that strong with the approach it's fundamental arguments.
vim-ultest
-
neotest: A modern, powerful testing plugin
How about https://github.com/rcarriga/vim-ultest ?
-
Your lualine custom features
I have one that's half working for ultest. I haven't bothered to get the colors right.
-
FAVOURITE PLUGINS
vim-test & vim-ultest (also essential for work)
-
Debugging in NeoVim
Vim-UltestHelps to debug quickly and easily
- Gathering suggestions for testing/tasks-running plugins
- Make live unit testing work in Neovim and you will have my undying appreciation.
-
debugpy.nvim: Command and API frontend to nvim-dap and Debugpy (debugging Python)
But I haven't yet set up anything properly other than Debugpy. nvim-dap is very barebones, so I feel that the best way is to have an extra configuration plugin on top. Debugpy.nvim is a very specific frontend plugin, but there are also more general plugins like nvim-metals and vim-ultest which also offer integration with nvim-dap.
-
What's the best tool for testing?
Love seeing my plugins in the wild! Just FYI for anyone reading vim-ultest has an integration with nvim-dap which allows you to write debugging configs for any language and debug tests. There are currently recipes for python and go but I'd love to see more added! https://github.com/rcarriga/vim-ultest/wiki/Debugging-Recipes
-
Populate quickfix from a tmux pane
Another thing I use for tests is https://github.com/rcarriga/vim-ultest which allows running the test and seeing the output inside vim, which works quite nice once I have narrowed down the test file that has the failing test.
- Java/Kotlin developers that use NeoVim as their main IDE, recommendations to someone that uses Intellij IDEA for java-dev but nvim for the rest?
What are some alternatives?
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
vim-test - Run your tests at the speed of thought [Moved to: https://github.com/vim-test/vim-test]
nvim - Simple and ready configuration for neovim(nvim) with LSP. Inited with rust and go support
nvim-dap-python - An extension for nvim-dap, providing default configurations for python and methods to debug individual test methods or classes.
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
neovim-remote - :ok_hand: Support for --remote and friends.
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
nvim-dap - Debug Adapter Protocol client implementation for Neovim
telescope-dap.nvim - Integration for nvim-dap with telescope.nvim
vim-test - Run your tests at the speed of thought
nvim-dap-virtual-text