Seongmin Lee

rest.nvim can’t understand non-standard mimetypes like `application/vnd.api+json`. You can use `[“vnd.api+json”] = “jq”` instead to format with `jq` from v2. v3 currently doesn’t support custom mimetypes

@mawkler setup above is using legacy config. So yes, there's no `result` field in config now. Since v3 release, you don't need to configure formatter specific for `rest.nvim`. `rest.nvim` can...

This has been fixed now. Be sure to disable auto url encoding in config: `request.hooks.encode_url = false` example config: ```lua vim.g.rest_nvim = { request = { hooks = { encode_url...

> Is it possible to also set the filetype of the response body to JSON in the case of `application/vnd.api+json`, just like for regular application/json responses? Current version will set...

@mawkler I don't think the absence of `content-length` header can be an issue. I made a simple web server with golang that responds with exactly this output but can't reproduce...

Yes! Thank you for providing those. So `rest.nvim` does know the response body type is `json` but it isn't formatting because you don't have any formatters attached to `json` filetype....

Old method is still supported (which just assigns given argument to `vim.g.rest_nvim`) but the config structure has been changed. ```lua require(“rest-nvim”).setup({ -- your config }) vim.g.rest_nvim = { -- your...

Those features are not removed but implemented as a different form now. See `:h rest-nvim.commands` ### Controlling result pane opening mode Now all window-opening rest.nvim user commands support command-modifiers (`:h...

pinning this issue as more people might have similar problems.

What formatter are you using? Do you have a formatter plugin or language server that should attached to any json buffer? What json string do you expect it to be...