neovim/test/functional/api
Justin M. Keyes 167a2383b9
fix(api): not using TRY_WRAP, generic error messages #31595
Problem:
- API functions using `try_start` directly instead of `TRY_WRAP`, do not
  surface the underlying error message, and instead show generic things
  like "Failed to set buffer".
- Error handling code is duplicated in the API impl, instead of
  delegating to the vim buffer/window handling logic.

Solution:
- Use `TRY_WRAP`.
2024-12-16 04:00:20 -08:00
..
autocmd_spec.lua fix(events): don't expand args.file for Lua callback (#31473) 2024-12-06 20:01:28 +08:00
buffer_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
buffer_updates_spec.lua test(api/buffer_updates_spec): prevent flakiness (#30521) 2024-09-26 18:34:35 +08:00
command_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
extmark_spec.lua feat(ui): sign/statuscolumn can combine highlight attrs #31575 2024-12-14 10:21:50 -08:00
highlight_spec.lua fix(api): make nvim_set_hl() respect all cterm attributes (#31390) 2024-12-02 08:24:58 +08:00
keymap_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
menu_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
proc_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
rpc_fixture.lua refactor: format test/* 2024-01-03 02:09:29 +01:00
server_notifications_spec.lua feat(api): broadcast events to ALL channels #28487 2024-05-17 07:37:39 -07:00
server_requests_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
tabpage_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
ui_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
version_spec.lua test(version_spec): expect vim.NIL, not nil, for "build" if not in a git clone 2024-12-03 06:31:09 -05:00
vim_spec.lua fix(api): don't try to get/set option for invalid option name (#31302) 2024-11-22 20:32:51 +08:00
window_spec.lua fix(api): not using TRY_WRAP, generic error messages #31595 2024-12-16 04:00:20 -08:00