Jacob Mealey

@jyn514 I see this ticket is a couple of years old, are you still willing to mentor it / is the work still relevant?

This is a request that has been brought up a couple of times. https://github.com/curl/trurl/issues/176#issuecomment-1527462342 the last one I could find was issue 176 where bagder recommended tabling a request for...

I've started looking into getting this working. it looks like [json-c](https://github.com/json-c/json-c) is a pretty popular library for this, so i've been using that. I think it makes sense for the...

I think `--force-replace` is a bit ugly, and probably needs better docs around how to use it. it _should_ handle something like that last example in some way. I wonder...

Right, but if we have `--set "query:foo=bar` be the counterpart to `--get "{query:foo}"` where it only does operations on the specified query parameter how would we replace the whole query?

Oh sorry, I misread `--set "query:foo=bar"` and kept reading it as `--set "query:=foo=bar"`. I understand what you are saying now.

another (clunky) solution may be a new flag`--allow-empty` for `--get` and `--set`? or something clever with the the modifiers in the get brackets `--get`, something like `--get "{empty:query} {empty:fragment}"` ?...

Something interesting I noticed is that is works for queries. I wonder if we're missing a memdupdec somewhere? I'd bet I broke this in this PR https://github.com/curl/trurl/pull/214 but maybe it's...

This looks like it's behavior from libcurl. I was able to get the same result with the following code. Should we open a ticked over there or are we just...

Ahh it could also be that `%18` maps to the ASCII character CAN (cancel), I'd bet curl doesn't play nice with decoding most control characters in the path. If you...