-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bug: formatter errors are not handled correctly #215
Comments
❌ The ticket to PR workflow is no longer supported. We have moved to a new chat interface in private beta. Please contact us at team@sweep.dev to try it out. 📖 For more information on how to use Sweep, please read our documentation. Tracking ID: 892484dfae
|
Could you share your config? @mariemachtmiau Also run
|
My config is basically just require("hurl").setup({
fixture_vars = {},
formatters = {
-- NOTE: for now use cat as error handling is broken when formatter is not found
html = { "cat" },
},
}) (also had debug and notifications turned on before when debugging). I use Nixvim to configure my Neovim and used the tag v2.0.0 to build the plugin. Checkhealth:
|
Logs:
Everything works completely fine with HurlVerbose and HurlVeryVerbose btw, also json (cuz it skips formatting there). |
Thanks @mariemachtmiau It should be okay now. |
Thanks for the quick fix @jellydn :) |
Details
When running HurlRunner the split opens but nothing happens. Debugged it and found it was getting stuck here
hurl.nvim/lua/hurl/utils.lua
Line 120 in 18d3e68
It tries to format html, even when setting
formatters = {},
in setup. Also doesn't seem to handle prettier not existing right, it just gets stuck (even with debug the last log is the one from L119.It works when I change the html formatter to
{ "cat" }
, but that's permanent, I'd like it to dynamically format if the executable exists and just ignore it if not (basically exactly what the code should already be doing).When running the commands manually
vim.v.shell_error ~= 0
is true, so it should normally work.The text was updated successfully, but these errors were encountered: