First pass on reorganizing the backend.

This is primarily renames and repackagings.

1 files changed, 0 insertions, 63 deletions

diff --git a/src/repo/login/store.rs b/src/repo/login/store.rs
deleted file mode 100644
index 47d1a7c..0000000
--- a/src/repo/login/store.rs
+++ /dev/null
@@ -1,63 +0,0 @@
-use sqlx::{sqlite::Sqlite, SqliteConnection, Transaction};
-
-use crate::{login::Id, password::StoredHash};
-
-pub trait Provider {
-    fn logins(&mut self) -> Logins;
-}
-
-impl<'c> Provider for Transaction<'c, Sqlite> {
-    fn logins(&mut self) -> Logins {
-        Logins(self)
-    }
-}
-
-pub struct Logins<'t>(&'t mut SqliteConnection);
-
-// This also implements FromRequestParts (see `./extract.rs`). As a result, it
-// can be used as an extractor for endpoints that want to require login, or for
-// endpoints that need to behave differently depending on whether the client is
-// or is not logged in.
-#[derive(Clone, Debug, Eq, PartialEq, serde::Serialize)]
-pub struct Login {
-    pub id: Id,
-    pub name: String,
-    // The omission of the hashed password is deliberate, to minimize the
-    // chance that it ends up tangled up in debug output or in some other chunk
-    // of logic elsewhere.
-}
-
-impl<'c> Logins<'c> {
-    pub async fn create(
-        &mut self,
-        name: &str,
-        password_hash: &StoredHash,
-    ) -> Result<Login, sqlx::Error> {
-        let id = Id::generate();
-
-        let login = sqlx::query_as!(
-            Login,
-            r#"
-                insert or fail
-                into login (id, name, password_hash)
-                values ($1, $2, $3)
-                returning
-                    id as "id: Id",
-                    name
-            "#,
-            id,
-            name,
-            password_hash,
-        )
-        .fetch_one(&mut *self.0)
-        .await?;
-
-        Ok(login)
-    }
-}
-
-impl<'t> From<&'t mut SqliteConnection> for Logins<'t> {
-    fn from(tx: &'t mut SqliteConnection) -> Self {
-        Self(tx)
-    }
-}