-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add participant attributes to the FFI #367
Conversation
d9405f8
to
e4bac56
Compare
44eb8b6
to
ce842e1
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.
logic lgtm. will leave the approval to someone who's more fluent with the Rust stack
livekit-ffi/src/server/room.rs
Outdated
)); | ||
}); | ||
server.watch_panic(handle); | ||
proto::UpdateLocalAttributesResponse { async_id } |
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.
more of a question/note about request/response semantics in the FFI layer
we are planning to allow set_attributes/set_metadata to be able to return failure & error string. This could be due to the participant not having permission to update that field. How do we reflect these errors on the Rust/FFI side?
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.
Rust FFI is already exposing the error, but this PR ignores it above
46b4f65
to
b1138c0
Compare
8fcce05
to
b1f4828
Compare
6d5db88
to
5323320
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.
lgtm otherwise.
use cargo fmt
a40d89f
to
2f5dbdb
Compare
8f6f18c
to
0a8a3fd
Compare
Also: