-
Notifications
You must be signed in to change notification settings - Fork 24
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
Documentation request - which parameters are actually respected? #530
Comments
➤ Automation for Jira commented: The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3851 |
Hi @hsghori, thanks for raising the issue. You can trust the public API. It's just that we need to update the source code doc for Note - |
I feel like these statements are contradictory. To me as a developer, the public functions in the SDK are "the public API". If those functions have arguments that are misleading then I don't have a lot of trust in the interface. |
Actually, we have a backlog task to update the source code documentation. As a part of that, we should be refactoring the old documentation. You can try these public methods and let us know if there is unpredictable behavior for the same 👍 |
I see a few parameters in the AblyRest client which (after digging through the source code) do not seem to be used anywhere (or if so how / where they're used is not obvious).
For example you define a keep alive parameter on the
AblyRest
client but that functionality seems to have been removed in 353100b .Similarly there is a
timeout
parameter onChannel.publish_messages
but when I dig into the underlying code, that parameter is overridden in the underlying http client.Now I may be missing something with how these parameters are actually used but as a consumer of ably I need to be able to trust the API and it's not obvious to me that the public API actually does what it says it does.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: