Skip to content

Domain Layer - use cases - business rules setup #29

Description

@AlexisTercero55

Core: Domain Layer

Support Reactive Navigation: Utilize the Domain Layer as the catalyst for routing. Use Cases drive session state changes in SessionManager, which MainActivity observes to perform reactive Compose Navigation transitions.

[NEW] Result.kt

  • Standardized success/failure wrapper for Use Cases.

[NEW] BaseUseCase.kt

  • Represents a single business transaction or user action.

[NEW] LoginUseCase.kt - Atomic Business Transaction:

  • Validate input using the Credentials domain model.
  • Execute authentication via the Data layer.
  • Apply Domain transformations (e.g., name formatting).
  • Commit the session state to the Single Source of Truth (SessionManager).

[NEW] LogoutUseCase.kt

  • Atomic termination of user session, triggering the reactive navigation flow.

Rho.Studio® - Engineering Department - Contact alexis.tercero@rho.studio

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Auth-featureUI compose feature - LoginViewModelDomain layerUse cases of business flowHome-featureCompose Home screen.

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions