Visitar URL original
Documentation request - which parameters are actually respected? · Issue #530 · ably/ably-pubsub-python · GitHub
Skip to content

Documentation request - which parameters are actually respected? #530

Description

@hsghori

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 on Channel.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

Activity

  1. sync-by-unito commented on Sep 14, 2023

    @sync-by-unito

    ➤ Automation for Jira commented:

    The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3851

  2. sacOO7 commented on Sep 15, 2023

    @sacOO7
    Contributor

    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 ably-python public methods. For the time being, you should refer to standard clientOptions as per official website doc =>
    https://ably.com/docs/api/rest-sdk?lang=python#client-options

    Note - keep_alive is no longer part of the standard public API. timeout param is also not part of the publish method, we will update both as a part of refactoring the source code doc 👍

  3. hsghori commented on Sep 18, 2023

    @hsghori
    Author

    You can trust the public API. It's just that we need to update the source code doc for ably-python public methods

    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.

  4. sacOO7 commented on Sep 18, 2023

    @sacOO7
    Contributor

    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 👍

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions