can Logger interface provide context?

[ynjgit]

can Logger interface provide context?, we can reuse the resty.Client , but different context with Request.SetContext, so we can print the ctx infomation (eg: trace_id).

like below:
// Logger interface is to abstract the logging from Resty. Gives control to
// the Resty users, choice of the logger.
type Logger interface {
Errorf(ctx context.Context, format string, v ...interface{})
Warnf(ctx context.Context, format string, v ...interface{})
Debugf(ctx context.Context, format string, v ...interface{})
}

[jeevatkm]

@ynjgit I think I can add it in the Resty v3. It will be a breaking change on the v3 release.

[jeevatkm]

@ynjgit BTW, I forgot to mention, I will align interface signature with Go's standard slog package for context param.

[jeevatkm]

@ynjgit I have tried the structure logger, it breaks the RESTY debug log text formatting completely because its a key-value pair, I need time to think about it context logger or not.

log package:

2026/04/25 16:26:27.864751 DEBUG RESTY 
==============================================================================
~~~ REQUEST(CURL) ~~~
	curl -X POST -H 'Accept-Encoding: gzip, deflate' -H 'Content-Type: application/json' -H 'Cookie: count=1' -H 'User-Agent: go-resty/3.0.0-beta.6 (https://resty.dev)' -d '{"name":"Resty"}' http://127.0.0.1:53709/curl-cmd-post
~~~ REQUEST ~~~
CORRELATION ID: 
POST  /curl-cmd-post  HTTP/1.1
HOST   : 127.0.0.1:53709
HEADERS:
	Accept-Encoding: gzip, deflate
	Content-Type: application/json
	Cookie: count=1
	User-Agent: go-resty/3.0.0-beta.6 (https://resty.dev)
BODY   :
{
   "name": "Resty"
}

ATTEMPT       : 1
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS       : 200 OK
PROTO        : HTTP/1.1
RECEIVED AT  : 2026-04-25T16:26:27.864648-07:00
DURATION     : 3.457125ms
HEADERS      :
	Content-Length: 0
	Date: Sat, 25 Apr 2026 23:26:27 GMT
	Set-Cookie: testserver=yes; Path=/; Domain=localhost; Expires=Sun, 26 Apr 2026 23:26:27 GMT
BODY         :
***** RESPONSE BODY IS ALREADY READ - see Response.{Result()/Error()} *****
==============================================================================

slog package:

time=2026-04-25T16:23:28.315-07:00 level=DEBUG msg="RESTY \n==============================================================================\n~~~ REQUEST(CURL) ~~~\n\tcurl -X POST -H 'Accept-Encoding: gzip, deflate' -H 'Content-Type: application/json' -H 'Cookie: count=1' -H 'User-Agent: go-resty/3.0.0-beta.6 (https://resty.dev)' -d '{\"name\":\"Resty\"}' http://127.0.0.1:53682/curl-cmd-post\n~~~ REQUEST ~~~\nCORRELATION ID: \nPOST  /curl-cmd-post  HTTP/1.1\nHOST   : 127.0.0.1:53682\nHEADERS:\n\tAccept-Encoding: gzip, deflate\n\tContent-Type: application/json\n\tCookie: count=1\n\tUser-Agent: go-resty/3.0.0-beta.6 (https://resty.dev)\nBODY   :\n{\n   \"name\": \"Resty\"\n}\n\nATTEMPT       : 1\n------------------------------------------------------------------------------\n~~~ RESPONSE ~~~\nSTATUS       : 200 OK\nPROTO        : HTTP/1.1\nRECEIVED AT  : 2026-04-25T16:23:28.314965-07:00\nDURATION     : 1.469834ms\nHEADERS      :\n\tContent-Length: 0\n\tDate: Sat, 25 Apr 2026 23:23:28 GMT\n\tSet-Cookie: testserver=yes; Path=/; Domain=localhost; Expires=Sun, 26 Apr 2026 23:23:28 GMT\nBODY         :\n***** RESPONSE BODY IS ALREADY READ - see Response.{Result()/Error()} *****\n==============================================================================\n"