Development Insight - Resty v3.0.0 #720
Pinned
jeevatkm
announced in
Announcements
Replies: 2 comments
-
Also need to decide if the requests objects are immutable as well as the client objects by the internal code. If it is, then we can reuse the request objects, otherwise make a clear statement in the documentation. I think the client object should be thread-safe via RW mutex, but the request should not. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm considering keeping the Request object's nature as-is, and I agree on the client object with RW mutex. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This discussion aims to provide high-level insight into v3.0.0 development. Feel free to engage and share ideas and inputs.
Branching Approach
master
to branchmain
.go.mod
on themain
branch will be updated togithub.com/go-resty/resty/v3
and go version.main
branch. When ready, PR will be created against themain
branch.Design Improvements (Possibly will result in breaking changes)
Client
client.BaseURL => client.BaseURL()
Middleware
middleware
with all the existing middleware will be exported, and the sub-function will be exposed as complete middleware.Retry, Redirect
And so on.
v3-selected
labeled issues will be focused from v3.0.0 Milestonev3-consideration
labeled issues will be focused on.internal
to park certain internal functionalityDocumentation and Website
go.mod
file.resty.dev
andgo-resty.org
, and I'm wondering which one to use it.So far, I have captured my thoughts and will continue to do so here.
Beta Was this translation helpful? Give feedback.
All reactions