remember me

Femto.Modules.Auth/Application/Services/IAuthService.cs

@@ -1,46 +0,0 @@
-using Femto.Modules.Auth.Application.Dto;
-using Femto.Modules.Auth.Models;
-
-namespace Femto.Modules.Auth.Application.Services;
-
-/// <summary>
-/// I broke off IAuthService from IAuthModule because the CQRS distinction is cumbersome when doing auth handling,
-/// particularly in regards to session management. I may or may not bother to move the commands and queries here also,
-/// but for controller actions I do quite like having the abstraction, and there is less drive within me to bother.
-/// It just seems redundant to expose them both, and it's a bit confusin'
-/// </summary>
-public interface IAuthService
-{
-    public Task<UserAndSession?> GetUserWithCredentials(
-        string username,
-        string password,
-        bool createLongTermSession,
-        CancellationToken cancellationToken = default
-    );
-    public Task<UserInfo?> GetUserWithId(
-        Guid? userId,
-        CancellationToken cancellationToken = default
-    );
-    public Task<Session> CreateStrongSession(Guid userId);
-    public Task<Session> CreateWeakSession(Guid userId);
-    public Task<Session?> GetSession(string sessionId);
-    public Task DeleteSession(string sessionId);
-
-    public Task<UserAndSession> CreateUserWithCredentials(string username,
-        string password,
-        string signupCode,
-        bool createLongTermSession,
-        CancellationToken cancellationToken = default);
-
-    public Task AddSignupCode(
-        string code,
-        string recipientName,
-        CancellationToken cancellationToken = default
-    );
-
-    public Task<ICollection<SignupCodeDto>> GetSignupCodes(
-        CancellationToken cancellationToken = default
-    );
-}
-
-public record UserAndSession(UserInfo User, Session Session);