-
-
Notifications
You must be signed in to change notification settings - Fork 626
Feature/connect improvements #254
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
Feature/connect improvements #254
Conversation
@pintsized let me know if there are any adjustments necessary |
@pintsized what do you think? |
Looks good, although we'll need to update the README and add some tests. Are you able to include them in this PR? I can help with the tests if you're not familiar with it? I don't think we really have proper coverage for return values from |
1e8a8f4
to
d12d6a9
Compare
@pintsized I tried adding UTs but I didn't have a good template to setup a local SSL server + use lua-resty-http as a client. If you can come up with a sample test for that - I can enhance and add more UTs. |
@pintsized once we merge this, I'll create a separate PR to fix #253 . I'm trying to avoid merge conflicts by doing one at a time. Do you think you'll have time to review this soon? |
@GuyLewin ok great, sounds good. And thank you! Yes, I promise I'll get to it soon, I'm just pretty busy atm. I'll see if I can get some SSL tests going on this though, so leave that to me. |
@pintsized sounds great, thanks! Let me know if there's any further changes needed in this repo. Otherwise I'll start working on the next one. |
@pintsized until this is approved, do you mind adding the |
Sure thing! Sorry again, I am getting there, just snowed under. Thanks for the contributions! |
Thanks! No worries, we forked these branches into our codebase for now until we merge it into the upstream. I'll also try closing and re-opening this PR in particular since I created it before Hacktoberfest. |
Solving #252 and #251