### Problem to solve It would be very helpful to be able to see the request that `glab api` is making, because the transform from `--field` to the json body is not intuitive For example, I'm trying to update branch protection as per [the docs](https://docs.gitlab.com/api/protected_branches/#example-update-a-push_access_level-record), I tried ``` glab api -X PATCH "/projects/:id/protected_branches/:branch" --field 'allowed_to_push=[{"user_id: :user}]' ``` but it says that `allowed_to_push is invalid` , but I have no idea why It would be really nice if I could see what was being sent without having to set up mitmproxy ### Proposal Add a `--verbose` flag that prints the request url and body that is being sent Might be worth just copying how curl handles `--verbose`, showing what is sent and what is recieved, so you can debug issues besides just the shape of the request being made? ### Further details ### Links / references