v2 planning #110
Unanswered
earthboundkid
asked this question in
Ideas
v2 planning
#110
Replies: 6 comments 1 reply
|
Drop ToHeaders and just have CopyHeaders. |
0 replies
|
Make BodyJSON etc into a Config. |
0 replies
|
Remove minitrue and slicex as part of going to Go 1.23 or whatever is out when this happens. |
0 replies
|
I should make an organization, so this can be a one time transfer. |
0 replies
|
Would love to see a more explicit way of extracting body of requests when it is considered error. Related to |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The package URL for this repo is now wonky between carlmjohnson and earthboundkid due to the user rename. I was thinking there wasn't a good way to fix this, but if the package moves to v2, the module path can be changed without annoying old users who try to upgrade their dependencies and get a module name mismatch error message.
If we move to v2 this, we might as well fix other problems like #81 at the same time.
What else should we clean up as part of v2?
All reactions