We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe.
When changing between librarys we should not expect users to define the channel options differently than the official grpc package itself.
Describe the solution you'd like
We should rewrite that to just use tuples as grpc itself does.
e.g. Link to the Documentation suggests tuple[tuple[...]] (('grpc.so_reuseport', 0),) but we expect Dict[str, Any].
(('grpc.so_reuseport', 0),)
pyzeebe/pyzeebe/channel/camunda_cloud_channel.py
Line 30 in de788a8
Additional context
https://grpc.github.io/grpc/python/glossary.html
I think it (changing options from dict to tuple) should be in another PR.
Originally posted by @dimastbk in #468 (comment)
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
When changing between librarys we should not expect users to define the channel options differently than the official grpc package itself.
Describe the solution you'd like
We should rewrite that to just use tuples as grpc itself does.
e.g. Link to the Documentation suggests tuple[tuple[...]]
(('grpc.so_reuseport', 0),)
but we expect Dict[str, Any].pyzeebe/pyzeebe/channel/camunda_cloud_channel.py
Line 30 in de788a8
Additional context
https://grpc.github.io/grpc/python/glossary.html
Originally posted by @dimastbk in #468 (comment)
The text was updated successfully, but these errors were encountered: