Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Connection options aren’t consistently named #477

Closed
bfontaine opened this issue Feb 5, 2019 · 2 comments · Fixed by #478
Closed

Connection options aren’t consistently named #477

bfontaine opened this issue Feb 5, 2019 · 2 comments · Fixed by #478

Comments

@bfontaine
Copy link
Contributor

👋 Hi again!

I just found a bug in our codebase because someone used :conn-manager instead of :connection-manager for some requests.

This is probably because there are already two options starting with :conn-: :conn-timeout and :conn-request-timeout.

I’d like to make a pull-request to uniformize those names:

  • Option 1: :conn-timeout, :conn-request-timeout, and :conn-manager
  • Option 2: :connection-timeout, :connection-request-timeout, and :connection-manager

Which option would be the best for you? I can also keep the current key(s) for backward compatibility.

@dakrone
Copy link
Owner

dakrone commented Feb 5, 2019

Hi @bfontaine,

I agree that we should be consistent here. My preference is probably for the fully-spelled version (:connection-timeout for example), I definitely think we should keep the current ones for backwards compatibility.

Perhaps clj-http.util/opt could be extended so multiple parameters can be passed to it and it will use either?

A PR would be most welcome!

@bfontaine
Copy link
Contributor Author

I made a PR: #478

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants