matrix-rust-sdk icon indicating copy to clipboard operation
matrix-rust-sdk copied to clipboard

feat[bindings]: expose power level thresholds in corresponding timeline event

Open JoFrost opened this issue 3 weeks ago • 2 comments

Hello! This PR exposes power-level thresholds in OtherState::RoomPowerLevels for the FFI timeline.

It includes action requirements such as ban, kick, invite, redact, state_default, events_default, per-event overrides and notifications. This gives FFI clients direct access to the effective power levels of a room, which were previously unavailable.

  • [x] Public API changes documented in changelogs (optional)

Signed-off-by:

JoFrost avatar Dec 05 '25 09:12 JoFrost

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 88.59%. Comparing base (cd9f433) to head (4c59282). :white_check_mark: All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5931      +/-   ##
==========================================
- Coverage   88.59%   88.59%   -0.01%     
==========================================
  Files         364      364              
  Lines      104341   104341              
  Branches   104341   104341              
==========================================
- Hits        92438    92437       -1     
- Misses       7537     7539       +2     
+ Partials     4366     4365       -1     

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

codecov[bot] avatar Dec 05 '25 09:12 codecov[bot]

CodSpeed Performance Report

Merging #5931 will not alter performance

Comparing JoFrost:main (4c59282) with main (cd9f433)

Summary

✅ 50 untouched

codspeed-hq[bot] avatar Dec 05 '25 09:12 codspeed-hq[bot]

Hello @poljar! Quick check on this PR.

I wanted to confirm whether this aligns with the intended API direction, or if you’d prefer to wait for #5937 to be merged and then have this rebased on top of it. If this approach doesn’t hit the mark, I’m happy to close the PR.

Thanks.

JoFrost avatar Dec 16 '25 22:12 JoFrost

I wanted to confirm whether this aligns with the intended API direction, or if you’d prefer to wait for #5937 to be merged and then have this rebased on top of it.

Yes, let's do that, I don't think there's much blocking #5937 so it should be merged soon™.

poljar avatar Dec 17 '25 08:12 poljar

All done @poljar. I rebased on main, and used what was introduced in #5937 for this PR.

JoFrost avatar Dec 21 '25 20:12 JoFrost