Package-level declarations
Types
Use case for deleting the user account.
Get the Default Protocol SupportedProtocol
This use case is responsible for retrieving the current user. fixme: Rename to ObserveSelfUserUseCase
Use case that allows getting the user details of a user, either locally or externally
Checks if the current user's team has enabled E2EI and MLS.
This use case is to get the file sharing status of the team settings from the local storage so we can use it to show and hide things on the screen
Checks if the current user has enabled MLS support.
Checks if the current requires password to authenticate operations. In case the user doesn't have a password, means is an SSO user.
Computes the managed_by property of the account to define if this is a read only account or not.
Checks if the self user is a team member or not.
Mark the MLS End-to-End Identity enabling status change as notified need to be called after notifying the user about the change e.g. after showing a dialog, or a toast etc.
Mark the file sharing status as notified need to be called after notifying the user about the change e.g. after showing a dialog, or a toast etc.
Mark the Self Deleting Messages team setting change as notified on the app. It needs to be called after notifying the user about that specific change, e.g. after showing a dialog, or a toast etc.
Observe E2EISettings to notify user when setting is changed to Enabled
This use case is to get a flow of file sharing status of the team settings from the local storage so we can use it to show and hide things on the screen
This use case is responsible for retrieving the current user and his/her team.
Use case that allows observing the user details of a user locally, or request it from API and save to DB, if there is no local data for such user.
This gets and observes the list of valid accounts, and it's associated team.
Persist migrated users from old datasource
This use case is responsible for retrieving the current user's server configuration.
Sets the user's handle remotely and locally.
Use case that returns Boolean if user should be asked for a feedback about call quality or not.
Syncs the current user's contacts.
This use case will sync the current user with the backend.
Updates the display name of the current user.
Updates the user's email address. keep in mind that this use case does not update the email immediately, it only sends a request to the backend. the use need to confirm the email change by clicking on the link in an email they receive.
Use case that updates next time when user should be asked for a feedback about call quality.
Updates the current user's UserAvailabilityStatus status.
Updates the supported protocols of the current user.
Update self supported protocols, and if the supported protocols did change we also resolve the active protocol for all one-on-one conversations.