You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've been working with go-resty and found the fmtBodyString function in the Request struct to be particularly useful. However, I noticed that it's currently a private function. I believe making this function public could benefit other users of the library.
Current Situation:
The fmtBodyString function is currently private and not accessible to users of the library.
Proposal:
Consider making the fmtBodyString function public, allowing users to access it directly.
Benefits:
Enhanced debugging capabilities: Users could leverage this function to inspect and format request bodies, which is particularly useful for debugging and logging purposes.
Custom implementations: Users could build upon this function for custom formatting or processing of request bodies.
Consistency: It would allow users to format body strings in the same way go-resty does internally, ensuring consistency across the application.
@Arpit529Srivastava Thanks for showing your interest. However, this request is not straightforward. Still, I have yet to decide to expose it. It does bring dependency on maintaining the API contract if it is exposed. I need to think about it.
You could look at other open issues and let me know which one you can tackle.
Hi,
I've been working with go-resty and found the
fmtBodyString
function in theRequest
struct to be particularly useful. However, I noticed that it's currently a private function. I believe making this function public could benefit other users of the library.Current Situation:
The
fmtBodyString
function is currently private and not accessible to users of the library.Proposal:
Consider making the
fmtBodyString
function public, allowing users to access it directly.Benefits:
Source
resty/request.go
Line 985 in baf7c12
The text was updated successfully, but these errors were encountered: