dogy_backend_api/service/assistant/daily_challenges/

store.rs

use super::Error as DailyChallengeError;
use crate::Error::DailyChallenge as Error;
use crate::Result;
use chrono::NaiveDate;
use sqlx::{query, query_as, Executor, Postgres, Transaction};
use uuid::Uuid;

// Database
pub async fn retrieve_timezone_from_user<'e, E>(conn: E, user_id: Uuid) -> Result<String>
where
    E: Executor<'e, Database = Postgres>,
{
    let timezone: (String,) = query_as("SELECT timezone FROM users WHERE id = $1;")
        .bind(user_id)
        .fetch_one(conn)
        .await
        .map_err(super::Error::from)?;

    if timezone.0.is_empty() {
        return Err(Error(DailyChallengeError::MissingTimezoneForUser));
    }

    Ok(timezone.0)
}

pub async fn set_local_timezone(txn: &mut Transaction<'_, Postgres>, timezone: &str) -> Result<()> {
    // We cant use bind here because timezone is not a param so we have to use format! macro.
    query(format!("SET LOCAL TIME ZONE '{}';", timezone).as_str())
        .execute(&mut **txn) // First, we deref to get the transaction and then deref again to get the connection
        .await
        .map_err(super::Error::from)?;

    Ok(())
}

pub async fn verify_daily_challenge_existence(
    txn: &mut Transaction<'_, Postgres>,
    user_id: Uuid,
    timezone: &str,
) -> Result<()> {
    set_local_timezone(txn, timezone).await?;

    let challenge_id: Option<(Uuid,)> = query_as(
        r#"SELECT id FROM user_daily_challenges
            WHERE user_id = $1 AND created_at::date = CURRENT_DATE;"#,
    )
    .bind(user_id)
    .fetch_optional(&mut **txn)
    .await
    .map_err(super::Error::from)?;

    match challenge_id {
        Some(id) => Err(Error(DailyChallengeError::ChallengeAlreadyCompleted {
            challenge_id: id.0,
        })),
        None => Ok(()),
    }
}

pub async fn retrieve_past_challenges<'e, E>(conn: E, user_id: Uuid) -> Result<Vec<String>>
where
    E: Executor<'e, Database = Postgres>,
{
    let past_challenges: Vec<(String,)> = query_as(
        r#"
        SELECT challenge
        FROM user_daily_challenges
        WHERE user_id = $1
        ORDER BY created_at DESC
        LIMIT 7;
    "#,
    )
    .bind(user_id)
    .fetch_all(conn)
    .await
    .map_err(super::Error::from)?;

    Ok(past_challenges.into_iter().map(|(c,)| c).collect())
}

pub async fn retrieve_daily_challenge_streaks(
    txn: &mut Transaction<'_, Postgres>,
    user_id: Uuid,
    timezone: &str,
) -> Result<Vec<NaiveDate>> {
    set_local_timezone(txn, timezone).await?;

    let streaks: Vec<(NaiveDate,)> = query_as(
        r#"
        SELECT created_at::date AS challenge_day
        FROM user_daily_challenges
        WHERE user_id = $1
        ORDER BY challenge_day;
    "#,
    )
    .bind(user_id)
    .fetch_all(&mut **txn)
    .await
    .map_err(super::Error::from)?;

    let dates: Vec<NaiveDate> = streaks.into_iter().map(|(d,)| d).collect();

    Ok(dates)
}

/// Saves the daily challenge for the user.
///
/// This requires a Postgres Transaction instead of connection because we are setting the time zone
/// on a transaction level.
pub async fn save_daily_challenge(
    txn: &mut Transaction<'_, Postgres>,
    user_id: Uuid,
    timezone: String,
    challenge: &str,
) -> Result<Uuid> {
    // Sets the timezone for the current transaction.
    set_local_timezone(txn, &timezone).await?;

    let challenge_id: (Uuid,) = query_as(
        r#"
        INSERT INTO user_daily_challenges (user_id, challenge)
        VALUES ($1, $2)
        RETURNING id;
        "#,
    )
    .bind(user_id)
    .bind(challenge)
    .fetch_one(&mut **txn)
    .await
    .map_err(super::Error::from)?;

    Ok(challenge_id.0)
}

// AI-related
pub static DAILY_CHALLENGE_PROMPT: &str = r#"
Create daily challenges and dog facts for dog owners. Challenges focus on activities such as learning a new trick, discovering a food recipe, or understanding dog behaviors.

# Steps
1. Identify Challenge Type: Determine whether the daily challenge will be a trick, recipe, behavior insight, or dog fact.
2. Craft a Challenge or Fact: Depending on the type, create a specific, actionable challenge or provide a fascinating, relevant dog fact.
    - For Tricks: Describe a step-by-step process to teach a new trick to a dog.
    - For Recipes: Offer a simple recipe that is healthy and suitable for dogs.
    - For Behaviors: Provide an informative piece about a specific dog behavior and how to positively address or encourage it.
    - For Dog Facts: Present a short, interesting fact about dogs that can intrigue or educate dog owners.
3. Ensure Variety: Rotate through different challenge types and facts to keep the daily content varied and engaging.

# Output Format
Each challenge or fact should be presented in a brief paragraph, clearly stating the type and giving detailed instructions, information, or an intriguing fact relevant to the challenge.

## Examples

### Example 1 (Trick)
Teach your dog the 'Shake Hands' trick. Start by getting them to sit, then hold a treat in your hand close to their nose. Tap their paw gently while saying 'shake.' When they lift their paw, praise them and give them the treat. Practice this a few times for them to learn.

### Example 2 (Recipe)
Create a simple dog treat using peanut butter and pumpkin puree. Mix 1 cup of pumpkin puree with 1/4 cup of natural peanut butter. Roll the mixture into small balls and place them on a baking sheet. Freeze for a quick and easy dog snack.

### Example 3 (Behavior)
Understand your dog's wagging tail. A wagging tail can indicate happiness, but the speed and direction of the wag can signify other emotions like anxiety or excitement. Observe your dog's wagging patterns to better understand their feelings.

### Example 4 (Fact)
Dogs have three eyelids, an upper lid, a lower lid, and a third lid, known as a nictitating membrane or haw, which helps keep the eye moist and protected.

# Notes
- Customize challenges based on common dog breeds and their attributes for increased relevance.
- Pay attention to seasonal changes, ensuring that challenges are practical and safe for the current weather.
- Ensure recipes use dog-safe ingredients only.
- Dog facts should aim to be surprising or educational.
- Only output one challenge.
- Only output the challenge or fact in paragraph form.
- Do not include any additional text or explanations and do not exceed 100 words.
"#;

pub static PET_INFO_PROMPT: &str = r#"
Here are the details about my pet. Use this information to create a personalized daily challenge or
dog fact for me."#;

pub static EXCLUDE_PAST_CHALLENGES_PROMPT: &str = r#"
Exclude generating these past challenges. Be sure to generate a unique challenge for today.
Here are the past challenges I have received: "#;