You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working with ably Python SDK has been pretty painless so far, except that very few of the types that are defined in ably/types are available to me, the developer.
I propose expanding the imports in init to include most (all?) types defined in ably/types.
For example: it is not possible to create a variable to store a Realtime channel with a correct type definition.
Hi @jamesroseman, Thanks for reporting the issue!
We do have pending issue to add strong type support. We will try to include fix for the same in future release 👍
It seems like that issue has been open for 241 days. Any indication on a timeline? I'm doing some prototyping to evaluate an Ably solution and having type support would greatly impact my assessment of its suitability. It doesn't seem like a big lift. I'd offer to put up a PR myself but it seems the last PR set to address this issue was reverted a few weeks after it was merged.
Working with ably Python SDK has been pretty painless so far, except that very few of the types that are defined in ably/types are available to me, the developer.
I propose expanding the imports in init to include most (all?) types defined in ably/types.
For example: it is not possible to create a variable to store a Realtime channel with a correct type definition.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: