Feat add recap view for pomodoro extention

[cchalop1]

Description

I have had a recap page for pomodoro extention.

The goal is to have a page for resume all the data from the your previous pomodoro cycle.

I have had 3 informations:

• number of cycle completed
• number of time (in minutes) completed
• numbers of back to back (cycles with less than 5 min between tow)

I thinks we can add more informations in futures but we can make a other PR for that.

fix #11054

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @KELiON @pernielsentikaer @brodelp @susonthapa @mikikiv @MartinGonzalez @Nathanjms you might want to have a look.

[pernielsentikaer]

Hi @cchalop1 👋

It looks good to me, @KELiON do you mind checking this?

[cchalop1]

Thanks for the typo ! @pernielsentikaer

[mikikiv]

Should this be filtered to only count interval.type === "focus"?

[pernielsentikaer]

Can you help here @cchalop1

[cchalop1]

Yes you are right. I'm going to fix it.

[cchalop1]

It is ok for you @mikikiv ?

[pernielsentikaer]

Just waiting for @KELiON do check it now 🙂

[pernielsentikaer]

I haven't tested it well yet, but we can maybe optimize stats-pomodoro-timer.tsx but using something like this which will:

• Avoid unnecessary iterations
• Use more descriptive variable names
• Use map, reduce, filter functions

import { usePromise } from "@raycast/utils";
import { getIntervalHistory } from "../lib/intervals";
import { Detail } from "@raycast/api";
import { Interval } from "../lib/types";

function calculateStats(intervals: Interval[]) {
  let completedCycles = 0;
  let totalFocusTime = 0;
  let backToBackCycles = 0;
  let prevEndAt = null;

  for (const interval of intervals) {
    for (const part of interval.parts) {
      if (part.endAt) {
        completedCycles++;
        totalFocusTime += interval.length;

        if (prevEndAt && part.startedAt - prevEndAt < 5 * 60 + 10) {
          backToBackCycles++;
        }

        prevEndAt = part.endAt;
      }
    }
  }

  return { completedCycles, totalFocusTime, backToBackCycles };
}

export default function StatsPomodoro() {
  const { data, isLoading } = usePromise(getIntervalHistory);
  const focusIntervals = data?.filter((interval) => interval.type === "focus") || [];

  const { completedCycles, totalFocusTime, backToBackCycles } = calculateStats(focusIntervals);

  const markdown = `# 🍅 Pomodoro Recap 🍅\n
  > 📊 Statistics of your pomodoro timer - all from the begin\n
   - You have completed **${completedCycles}** pomodoro cicle${completedCycles > 1 ? "s" : ""}. ✨\n
   - Total of **${totalFocusTime / 60}m** of focus time. ⏱️\n
   - Top Number of back to back pomodoro cicle${backToBackCycles > 1 ? "s" : ""}: **${backToBackCycles}**. 👑\n
    `;

  return <Detail isLoading={isLoading} markdown={markdown} />;
}

[cchalop1]

I haven't tested it well yet, but we can maybe optimize stats-pomodoro-timer.tsx but using something like this which will:

• Avoid unnecessary iterations
• Use more descriptive variable names
• Use map, reduce, filter functions

import { usePromise } from "@raycast/utils";
import { getIntervalHistory } from "../lib/intervals";
import { Detail } from "@raycast/api";
import { Interval } from "../lib/types";

function calculateStats(intervals: Interval[]) {
  let completedCycles = 0;
  let totalFocusTime = 0;
  let backToBackCycles = 0;
  let prevEndAt = null;

  for (const interval of intervals) {
    for (const part of interval.parts) {
      if (part.endAt) {
        completedCycles++;
        totalFocusTime += interval.length;

        if (prevEndAt && part.startedAt - prevEndAt < 5 * 60 + 10) {
          backToBackCycles++;
        }

        prevEndAt = part.endAt;
      }
    }
  }

  return { completedCycles, totalFocusTime, backToBackCycles };
}

export default function StatsPomodoro() {
  const { data, isLoading } = usePromise(getIntervalHistory);
  const focusIntervals = data?.filter((interval) => interval.type === "focus") || [];

  const { completedCycles, totalFocusTime, backToBackCycles } = calculateStats(focusIntervals);

  const markdown = `# 🍅 Pomodoro Recap 🍅\n
  > 📊 Statistics of your pomodoro timer - all from the begin\n
   - You have completed **${completedCycles}** pomodoro cicle${completedCycles > 1 ? "s" : ""}. ✨\n
   - Total of **${totalFocusTime / 60}m** of focus time. ⏱️\n
   - Top Number of back to back pomodoro cicle${backToBackCycles > 1 ? "s" : ""}: **${backToBackCycles}**. 👑\n
    `;

  return <Detail isLoading={isLoading} markdown={markdown} />;
}

Yes I agree with you, it is clearer if we put everything in the calculatesStats function. I push for change

[pernielsentikaer]

I hope I didn't break something since I didn't have any data to test with 🙂 Is this ready for another review?

[cchalop1]

I have tested with my local data and i work well. Yep it is ready !

[pernielsentikaer]

Hi 👋

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/asubbotin/pomodoro

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@cchalop1).
Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.