-
Notifications
You must be signed in to change notification settings - Fork 126
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
Move VideoCallClient
into its own crate
#142
Conversation
… callback hell With some code cleanups along the way
Conform `use` statements in yew-ui to crate
Ok, I'll take a look, thanks for this huge contribution @ronen !! |
@ronen @griffobeid I think that you guys should talk about #144 |
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.
This looks great, thanks for adding all of the awesome documentation!
|
||
--- | ||
|
||
This crate provides a client-side (browser) interface to the videocall protocol. The purpose is to |
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.
We could be more specific here and say that it only supports Chrome due to some web APIs we use at the moment
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.
Yeah, good point. Added.
This reverts commit 8ece33d.
This reverts commit 8ece33d.
…)" This reverts commit 672a732.
This is a continuation of #137. It's the same code, but takes it to the next step: Crate-ified the
VideoCallClient
stuff: Moved all the code fromyew-ui/src/model
into a new top-level workspace & cratevideocall-client
. And added documentation! And of course also conformedyew-ui
to use the new crate.For ease of seeing what's going on here, I've based this PR off the
client
branch. Dunno whether you'd want to merge this onto that branch for merging as part of #137, or I can change this to be based off main and merging this would supercede #137, or wait until #137 is merged on its own then I can rebase all this off ofmain
and update this PR. I have no strong opinions. But it's done and working so figured I'd put it out for eyeballs now :)