Group Group Group Group Group Group Group Group Group

Alternative Use Case pattern to handle multiple action

Hi, sorry for the confusing title
in the last chapter about use case element, there is this example

class SignInUseCase: UseCase {
// input data variable
// side effect subsytem variable
// progress closure variable
// init method
// start method
}

I understand the objective of this command pattern, where you put all the state, then execute it based on the input data. But I want to achieve where I don’t need to create a use case for a single action. So I am looking for an alternative pattern that looks like with this pattern where I can put multiple actions on it, just like below

class AuthUseCase {
// sign-in method
// log out method
// read user session
}

I know that the above code is the repository pattern, but I need it to contain multiple use case to avoid bloated use case in the project. Thanks

I just thinking that the pattern I am looking for actually making the code low cohesion, since it will contain more than 1 functionality, someone can delete this question

@rcach Can you please help with this when you get a chance? Thank you - much appreciated! :]

@shogunkaramazov :+1:. @raffi, if there’s anything I can answer please feel free to reply, I think you’ve indicated that you’ve resolved your question but happy to answer any questions. Cheers!