matrix-org / matrix-org/matrix-rust-sdk
[widget bindings] Extract the business logic present in this crate to a new place
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
The bindings should be a thin layer between foreign language and rust SDK.
It is not a good place to put common logic for the EX apps.
E.g this should be moved to another crate/project
https://github.com/matrix-org/matrix-rust-sdk/blob/b0c0e0e0c4e765d37958f30ce420701f80f1f937/bindings/matrix-sdk-ffi/src/widget.rs#L147C8-L147C45
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing bindings/matrix-sdk-ffi/src/widget.rs at the linked code location and tracing the surrounding widget binding logic. Determine which logic is common business behavior versus foreign-language binding code, then identify the appropriate new crate or project. Done means the business logic is extracted and the bindings remain a thin layer, but the destination is not specified by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100