feat(curl): add option to debug call#1392
Conversation
be773da to
608cb7e
Compare
|
This PR was marked as stale after 7 days of inactivity and will be closed after another 7 days of further inactivity. If this PR should be kept open, just add a comment, remove the stale label or push new commits to it. |
608cb7e to
e971b6a
Compare
863ba9e to
502a8fa
Compare
502a8fa to
648268c
Compare
|
This PR was marked as stale after 7 days of inactivity and will be closed after another 7 days of further inactivity. If this PR should be kept open, just add a comment, remove the stale label or push new commits to it. |
|
|
||
| if model.Verbose { | ||
| requestDump, _ := httputil.DumpRequest(req, true) | ||
| params.Printer.Outputln(fmt.Sprintf("--- REQUEST ---\n%s", string(requestDump))) |
There was a problem hiding this comment.
When dumping a request/response with a binary body this has the chance to bring the terminal into a weird state.
But looking at outputResponse this doesn't seem to matter
|
|
||
| if model.Verbose { | ||
| responseDump, _ := httputil.DumpResponse(resp, false) | ||
| params.Printer.Outputln(fmt.Sprintf("--- RESPONSE ---\n%s", string(responseDump))) |
There was a problem hiding this comment.
what's the difference between stackit curl --include and stackit curl --verbose for the response?
Description
Small PR to add similar feature as
curl -vChecklist
make fmtmake generate-docs(will be checked by CI)make test(will be checked by CI)make lint(will be checked by CI)