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
The items in dictionaries returned from qBittorrent are not defined or typed. This makes interacting with this these response payloads more cumbersome and opaque than necessary.
Describe the solution you'd like
Type hints exist for the response payloads such that IDEs and type checkers can use them.
As suggested in #337, the response payload definitions would subclass TypedDict. While this approach probably makes the most sense, it conflicts with the existing design of response definitions which subclass AttrDict. Currently, it is not possible to multiple inheritance with TypedDict unless all base class are subclasses of TypedDict. So, I'm not really sure the best way to achieve this....unless the AttrDict stuff is dropped....but that would be a huge break in backwards compatibility that'd I'd like to avoid.
Describe alternatives you've considered
Status quo
Additional context
No response
The text was updated successfully, but these errors were encountered:
What is the problem or limitation you are having?
The items in dictionaries returned from qBittorrent are not defined or typed. This makes interacting with this these response payloads more cumbersome and opaque than necessary.
Describe the solution you'd like
Type hints exist for the response payloads such that IDEs and type checkers can use them.
As suggested in #337, the response payload definitions would subclass
TypedDict
. While this approach probably makes the most sense, it conflicts with the existing design of response definitions which subclassAttrDict
. Currently, it is not possible to multiple inheritance withTypedDict
unless all base class are subclasses ofTypedDict
. So, I'm not really sure the best way to achieve this....unless the AttrDict stuff is dropped....but that would be a huge break in backwards compatibility that'd I'd like to avoid.Describe alternatives you've considered
Status quo
Additional context
No response
The text was updated successfully, but these errors were encountered: