Closed
Bug 1866521
Opened 1 year ago
Closed 1 year ago
Decide on a new high-level FxA API
Categories
(Application Services :: Fxa Client, enhancement, P3)
Application Services
Fxa Client
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markh, Assigned: bdk)
References
(Depends on 1 open bug)
Details
From github: https://github.com/mozilla/application-services/issues/5395.
We want to expand the functionality of our FxA client code so that consumers can use it without needing so much wrapper code. In order to do that, we need to decide what the API should be.
Some guidelines:
- The API should be roughly comparable to the High level FxAAccountAManager API from android-components.
- The API should be relatively easy to integrate on iOS and Android (hopefully Desktop as well, but that's secondary).
- The API should be compatible with UniFFI
┆Issue is synchronized with this Jira Task
┆Epic: Wrapper-less FxA
Change performed by the Move to Bugzilla add-on.
| Reporter | ||
Updated•1 year ago
|
Assignee: nobody → bdeankawamura
| Assignee | ||
Comment 1•1 year ago
|
||
This is done, and the new API is simply the process_event method as discussed in the RFC.
| Assignee | ||
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•