From 6c65e97e49d1d56380aa7d71abb0394b08ff60ca Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Sun, 24 Aug 2025 16:00:45 -0400 Subject: Return an identity, rather than the parts of an identity, when validating an identity token. This is a small refactoring that's been possible for a while, and we only just noticed. --- src/invite/handlers/accept/test.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/invite/handlers/accept/test.rs') diff --git a/src/invite/handlers/accept/test.rs b/src/invite/handlers/accept/test.rs index adc7aa4..5140e3f 100644 --- a/src/invite/handlers/accept/test.rs +++ b/src/invite/handlers/accept/test.rs @@ -37,12 +37,12 @@ async fn valid_invite() { let secret = identity .secret() .expect("newly-issued identity has a token secret"); - let (_, login) = app + let identity = app .tokens() .validate(&secret, &fixtures::now()) .await .expect("newly-issued identity cookie is valid"); - assert_eq!(name, login.name); + assert_eq!(name, identity.user.name); // Verify that the given credentials can log in @@ -51,12 +51,12 @@ async fn valid_invite() { .login(&name, &password, &fixtures::now()) .await .expect("credentials given on signup are valid"); - let (_, login) = app + let identity = app .tokens() .validate(&secret, &fixtures::now()) .await .expect("validating a newly-issued token secret succeeds"); - assert_eq!(name, login.name); + assert_eq!(name, identity.user.name); } #[tokio::test] -- cgit v1.2.3