Caio Raposo comments

Results 6 comments of


                                            Caio Raposo

vis_pipe() doesn't correctly handle programs that fork to the background

Sorry for being a little late, but thanks for the response. Do you think we should handle possible error messages from stderr as suggested by [bugaevc](https://github.com/bugaevc/wl-clipboard/pull/110)?

vis_pipe() doesn't correctly handle programs that fork to the background

@mcepl I still have this issue so I put the following in my visrc: ``` vis:map(vis.modes.NORMAL, 'Y', ':> wl-copy 2>/dev/null -n') ```

Adding .and(warp::body::json()) causes CORS to stop being allowed

I can confirm this, having the same issue.

Adding .and(warp::body::json()) causes CORS to stop being allowed

Oh you just need to tell cors to allow the `content-type` header, because we are using the json body, like this: ```rust let cors = warp::cors() .allow_methods(&[Method::POST]) .allow_header("content-type"); ``` If...

Adding .and(warp::body::json()) causes CORS to stop being allowed

Try adding this header to fetch: ```javascript fetch("http://127.0.0.1:8081/apples", { method: "POST", body: JSON.stringify({num: 25}), headers: {"Content-type": "application/json; charset=UTF-8"} }) ```

Adding .and(warp::body::json()) causes CORS to stop being allowed

Nice, that was a little tricky for me as well. I'm not sure about documentation either, maybe a adding a example to the repo would be enough.