Skip to content
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

sdk: implement MSC3489 live location sharing #3621

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

torrybr
Copy link
Contributor

@torrybr torrybr commented Jun 28, 2024

Add support for MSC3489 live location sharing. Requesting an initial review to clarify some technical questions and help get this over the finish line.

Building on this Ruma PR

  • Public API changes documented in changelogs (optional)

Signed-off-by:

@torrybr torrybr marked this pull request as ready for review July 1, 2024 12:55
@torrybr torrybr requested a review from a team as a code owner July 1, 2024 12:55
@torrybr torrybr requested review from poljar and removed request for a team July 1, 2024 12:55
@torrybr torrybr changed the title Draft: Support for MSC3489 live location sharing Support for MSC3489 live location sharing Jul 1, 2024
@torrybr torrybr marked this pull request as draft July 1, 2024 13:07
@torrybr torrybr changed the title Support for MSC3489 live location sharing Draft: Support for MSC3489 live location sharing Jul 1, 2024
@torrybr torrybr marked this pull request as ready for review July 1, 2024 15:31
@torrybr torrybr changed the title Draft: Support for MSC3489 live location sharing Support for MSC3489 live location sharing Jul 1, 2024
Copy link

codecov bot commented Jul 1, 2024

Codecov Report

Attention: Patch coverage is 73.21429% with 15 lines in your changes missing coverage. Please review.

Project coverage is 84.23%. Comparing base (d8b2b74) to head (df93412).
Report is 164 commits behind head on main.

Files Patch % Lines
crates/matrix-sdk-ui/src/timeline/beacons.rs 66.66% 8 Missing ⚠️
crates/matrix-sdk-ui/src/timeline/event_handler.rs 88.00% 3 Missing ⚠️
crates/matrix-sdk-base/src/rooms/mod.rs 33.33% 2 Missing ⚠️
crates/matrix-sdk/src/room/mod.rs 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3621      +/-   ##
==========================================
- Coverage   84.25%   84.23%   -0.03%     
==========================================
  Files         259      260       +1     
  Lines       26592    26648      +56     
==========================================
+ Hits        22406    22446      +40     
- Misses       4186     4202      +16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@poljar poljar requested review from bnjbvr and removed request for poljar July 9, 2024 10:38
Copy link
Member

@bnjbvr bnjbvr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! supporting live location sharing in the SDK will be grand!

So, I appreciate the amount of code you've written here, and that it might be sufficient to have the basic feature working. However, I think the work here could be split (to make reviews faster) and layered in different ways:

  • support for the base crate and SDK could go in a separate PR
  • sending the beacon events themselves could happen in the SDK main crate too (I haven't seen any code for this, I think?)
  • better handling of beacon events coming before their associated beacon info event could be another PR.
  • then support for the timeline / FFI bindings

Each PR would also have tests at its own level, to make sure that it's behaving as intended. We're requiring tests for major functionality like this, otherwise it's too big a risk to discover later that it may be broken in subtle ways.

In fact, I think there's also potential for a more ergonomic, higher level API for beacons:

  • provide a stream to listen to new live location shares (client wide)
  • for each live location share, a stream to listen to new beacon events, and updates about the beacon info itself (stopped/redacted/etc.)

Then, the timeline could spawn a task, and provide UI updates based on both stream updates.

How does that sound?

crates/matrix-sdk-base/src/rooms/mod.rs Show resolved Hide resolved
crates/matrix-sdk/src/room/mod.rs Show resolved Hide resolved
crates/matrix-sdk/src/room/mod.rs Show resolved Hide resolved
crates/matrix-sdk/src/room/mod.rs Show resolved Hide resolved
crates/matrix-sdk/src/room/mod.rs Show resolved Hide resolved
user_id: OwnedUserId,
) {
let mut beacon_state = BeaconState::new(c, user_id.clone());
if let Flow::Remote { event_id, .. } = self.ctx.flow.clone() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: use &self.ctx.flow instead of cloning

});

if !found {
warn!("Did not find beacon_info event in timeline items. Adding to pending list");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

warn should be kept for non-fatal errors.

Suggested change
warn!("Did not find beacon_info event in timeline items. Adding to pending list");
debug!("Did not find beacon_info event in timeline items. Adding to pending list");

Comment on lines +48 to +53
let Some(location) = beacon_state.last_location() else {
return TimelineItemContentKind::FailedToParseMessageLike {
event_type: "org.matrix.msc3672.beacon".to_string(),
error: "Could not find beacon last location content".to_string(),
};
};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the last location was not set, then I think the TimelineItemContent should not exist in the first place.

Comment on lines +538 to +541
pub async fn send_user_location_beacon(
self: Arc<Self>,
geo_uri: String,
) -> Result<(), ClientError> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's way too much logic in this function; it should not live at the FFI layer, otherwise it's ~impossible to test.

Comment on lines +1 to +2
//! This module handles rendering of MSC3489 live location sharing in the
//! timeline.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think having this in the timeline is the proper cutting point. Instead, this would be more useful to have at the SDK layer, and maybe even with a slightly different API.

@bnjbvr
Copy link
Member

bnjbvr commented Jul 11, 2024

Also, we'd need some way to implement redaction of all the beacon events related to a beacon info event, as indicated by the MSC.

@torrybr
Copy link
Contributor Author

torrybr commented Jul 12, 2024

@bnjbvr Thanks for taking time to provide such detailed feedback! I agree with all your points and can work on splitting this up into simpler PRs and layer it as described. The stream API is good approach and would make life a lot easier 😃

@torrybr
Copy link
Contributor Author

torrybr commented Jul 18, 2024

In fact, I think there's also potential for a more ergonomic, higher level API for beacons:

  • provide a stream to listen to new live location shares (client wide)
  • for each live location share, a stream to listen to new beacon events, and updates about the beacon info itself
    (stopped/redacted/etc.)

@bnjbvr Do you have an example of streams being used in the codebase? This should help me get some more direction once I get to this.

@bnjbvr
Copy link
Member

bnjbvr commented Jul 22, 2024

@bnjbvr Do you have an example of streams being used in the codebase? This should help me get some more direction once I get to this.

You can look for functions which names end up with _stream :)

@torrybr
Copy link
Contributor Author

torrybr commented Aug 6, 2024

@bnjbvr I'm working on handling beacon events and associating them with their beacon info events, as mentioned in

better handling of beacon events coming before their associated beacon info event could be another PR

Any guidance on where to place this logic specifically where I should be grabbing the beacon events from?

@bnjbvr
Copy link
Member

bnjbvr commented Aug 14, 2024

@bnjbvr I'm working on handling beacon events and associating them with their beacon info events, as mentioned in

better handling of beacon events coming before their associated beacon info event could be another PR

Any guidance on where to place this logic specifically where I should be grabbing the beacon events from?

Sweet! I suppose that could go in a subsequent step, when it's time to display/render the beacons themselves, in the timeline. As far as I understand, the support should be pretty minimal/straightforward in the SDK, and ordering is only important as soon as you want to display something, right? Happy to chat about this in the Matrix SDK dev room, if needs be.

@bnjbvr bnjbvr changed the title Support for MSC3489 live location sharing sdk: implement MSC3489 live location sharing Sep 3, 2024
@torrybr torrybr mentioned this pull request Sep 4, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants