-
-
Notifications
You must be signed in to change notification settings - Fork 148
Sending JSON-payload #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same here. The issue comes from plenary. It doesn't seem to support JSON. Instead, it generates The issue was caused by commit 33c6829 / issue #102. Instead of a string, a table is returned which triggers plenary's behavior. |
Thanks for the heads up! At least for now, I reverted back to commit |
Same here! Is there any workaround for it? Beside downgrade rest.nvim? |
Same here! |
@NTBBloodbath Please revert merging my latest PR, It is the root cause for the issue. |
any progress on this ? I remember reading that maintainer is done with this repo (on reddit) and this would correlate with 12 old last commit. Any forks if so ? |
You can consider this fork to resolve this issue: https://github.com/teto/rest.nvim/tree/always-send-string |
I just installed the plugin for the first time and have this bug. |
Headers on - Content-Type: application/json
+ content-type: application/json |
Hello! I just installed this plugin, and it works pretty well so far! I'm having some issues though, not sure if I'm understanding this plugin correctly. I'm trying to send some data as json, like this:
I get a response like this in the response window:
I was expecting to get the same data back in the
json
-field of the response, but it'snull
as you can see. I checked the output ofRestNvimPreview
and it gave me this:curl -sSL --compressed -X 'POST' -H 'Content-Type: application/json' -d 'name=Test' 'http://httpbin.org/post'
. Trying to send that from the command line gives me the same response as before.I kinda figured with the
Content-Type
header, the data would be sent as json, but it seems like that's not the case. Is this intended behavior, or have I misunderstood something? It's a great plugin nonetheless, thanks for creating it!The text was updated successfully, but these errors were encountered: