plenary.nvim
plenary.nvim copied to clipboard
nvim-lua
plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.
Example usage: ```lua -- Just to make examples cleaner local function dump(x) print(vim.inspect(x)) end -- curry/curry2 dump(vim.tbl_map(f.curry(tostring), {1, 2, 3, 4})) -- '{ "1", "2", "3", "4"}' local function add(x,...
Calling something like `curl.post` synchronously (i.e without a callback) has a maximum timeout of 10s as the curl call is wrapped by a job with a 10s timeout. ```lua --...
When I define `'shellslash'`, Windows paths look like `C:/Users/user/...`. This results in multiple failures starting from incorrect `path.sep` detected, leading to errors like: ``` E5108: Error executing lua ...a/site/pack/paqs/start/plenary.nvim/lua/plenary/path.lua:490: Could...
The recommended way plenary has for running tests (e.g. `nvim --headless --noplugin -u scripts/minimal_init.vim -c "PlenaryBustedDirectory lua/tests/ { minimal_init = './scripts/minimal_init.vim' }"`) makes it easy I think to run into...
Hello everyone, I have a plugin that has a lot of tests and it would be easier if I could configure `PlenaryBustedDirectory` to show only the tests that failed instead...
Something like on_insert but to modify the strings that are inserted in the output table. Yes, we could always just another ipairs loop and do that, but more convenient this...
I was trying to find an issue that is tracking support for `setup` and `teardown` methods, but couldn't find anything thus far. Any particular reason those two methods aren't supported?...
As of now there is no test coverage, ie with `luacov`. Further I noticed the following files have no test coverage and neither documentation in the README: 1. benchmark 2....
It'd be nice to have a way with plenary's busted support to specify dependencies that test cases have on active plugins. E.g., imagine a spec file for a function `foo`...