Closed joninvski closed 2 weeks ago
Can confirm this. The example is right, but that's a regression in the code. If you lower-case the content-type header it will work. But as said, it's a regression, will fix it later, when I'm back at home.
I have just discovered that this problem does not occur if file size is small. It happened when image was 500kb but once i reduced it to 20k problem stopped.
Currently in main. It works this way with binary files (like images):
# @file-to-variable LOGO_FILE_VAR ./sample_image.png binary
POST https://httpbin.org/post
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary{{$timestamp}}
------WebKitFormBoundary{{$timestamp}}
Content-Disposition: form-data; name="logo"; filename="logo.png"
Content-Type: image/jpeg
{{LOGO_FILE_VAR}}
------WebKitFormBoundary{{$timestamp}}--
Note the binary
keyword at the end of the metatag directive.
This tells kulala to read it as binary, instead of just a raw string.
For text files like json or txt or what not, you can completely ignore that and just read them as before:
# @file-to-variable SOME_JSON_VAR ./some.json
[!WARNING] neovim might get really laggy when you read big files. I tested it with files around 1-2 Megabytes which worked fine; when testing it with files around 5-10 Megabytes it freezes for some seconds :see_no_evil:
When trying this small example:
I get this error:
I am running on neovim
0.10.2
and installing kulala via lazyvim rest extra.Thanks