-
Notifications
You must be signed in to change notification settings - Fork 28
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
Device connect lazily #294
Conversation
88cd870
to
2257ba0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, nearly there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had the idea that the following is probably nicer 🤔
Since we're awaiting the task in init anyway, we only need to store whether or not it was successful
71b02a6
to
1ee4b02
Compare
76aaade
to
f1dfd97
Compare
4786964
to
f765121
Compare
f765121
to
8cf8ea7
Compare
0b341bd
to
b3fa65e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please could you also update Signal.connect
to take the same arguments as Device.connect
?
I have added it to Signal.connect which has mockbackend and backend but they don't use the param force_reconnect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought of a bug...
closes #265