-
Notifications
You must be signed in to change notification settings - Fork 180
Add new NativeCurlClient #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Update README.md Replace Redmine\Client with NativeCurlClient in docs Fix some spelling errors
|
Hey @kbsali this PR is ready for review. I've implemented nearly all existing features from the old client in the new I've also created a migration doc and changed the README to not mention the old client anymore. |
kbsali
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
amazing job! :)
👍
Co-authored-by: Kevin Saliou <kevin@saliou.name>
kbsali
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for taking the time to apply some of my comments! :) 👍
|
Can I resolve all open conversations and merge this PR? |
|
please do yes! :) |
Goal of this PR is a new NativeCurlClient like the existing one, that will work native with curl without other dependencies. I'm still at the work figuring out the necessary public method that will be needed. In the next major release this client should replace the existing
Redmine\Client.In the best case every curl options could be managed with
setCurlOption()andunsetCurlOption(), but now I have to create a way to manage the possible setted headers.