Skip to content
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

Proposal: Switch from Retrofit2 to OkHttp3 #1161

Open
tokuhirom opened this issue Nov 19, 2023 · 0 comments
Open

Proposal: Switch from Retrofit2 to OkHttp3 #1161

tokuhirom opened this issue Nov 19, 2023 · 0 comments

Comments

@tokuhirom
Copy link
Member

When the SDK was first developed, we utilized Retrofit2 to improve implementation efficiency. However, nowadays, our API definitions are automatically generated from openapi YAML files, and the use of Retrofit2 has become less relevant.

Furthermore, with the lack of new versions of Retrofit2 since 2020, it might be a good time for us to consider alternatives. In my opinion, switching to OkHttp3 could bring about improvements in both code readability and maintainability.

I propose that we migrate from Retrofit2 to OkHttp3 for our HTTP client. I look forward to hearing the thoughts of others on this proposal. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants