Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions backend/api/account/serializers.py
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,15 @@ class ActiveSessionSerializer(serializers.Serializer):
client_version = serializers.CharField(
required=False, allow_null=True, default=None
)
created_at = serializers.DateTimeField(required=True)
last_used = serializers.DateTimeField(required=True)
is_current = serializers.BooleanField(required=True)


class ActiveSessionListSerializer(serializers.Serializer):
sessions = serializers.ListField(
child=ActiveSessionSerializer(), required=True, allow_empty=False
current_session = ActiveSessionSerializer(required=True)
other_sessions = serializers.ListField(
child=ActiveSessionSerializer(), required=True, allow_empty=True
)


Expand Down
26 changes: 23 additions & 3 deletions backend/api/account/views.py
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@
from api.settings import (
ACCOUNT_COOKIE_NAME,
AUTHED_PWD_RESET_EXP_SECONDS,
GENERIC_ERR_RESPONSE,
LONG_SESS_EXP_SECONDS,
SEND_EMAILS,
SESS_EXP_SECONDS,
Expand Down Expand Up @@ -107,11 +108,13 @@ def get_active_sessions(request):
user_account=user,
).order_by("-last_used")

active_sessions = []
current_session = None
other_sessions = []

for session in sessions:
session_data = {
"public_id": session.public_id,
"created_at": session.created_at,
"last_used": session.last_used,
"is_current": session.session_token
== request.COOKIES.get(ACCOUNT_COOKIE_NAME),
Expand All @@ -123,9 +126,26 @@ def get_active_sessions(request):
session_data["os_version"] = device.os_version() or None
session_data["client_name"] = device.client_name() or None
session_data["client_version"] = device.client_version() or None
active_sessions.append(session_data)

return Response({"sessions": active_sessions}, status=200)
if session_data["is_current"]:
if current_session is not None:
logger.error(
f"Multiple sessions matching session token for user: {user.id}."
)
current_session = session_data
else:
other_sessions.append(session_data)

if current_session is None:
logger.error(
f"No session matching session token for user, despite being authenticated: {user.id}."
)
return GENERIC_ERR_RESPONSE

return Response(
{"current_session": current_session, "other_sessions": other_sessions},
status=200,
)


@api_endpoint("POST")
Expand Down
11 changes: 8 additions & 3 deletions frontend/src/app/settings/(submenus)/security/page.tsx
Original file line number Diff line number Diff line change
@@ -1,8 +1,11 @@
"use client";

import ChangePasswordDialog from "@/features/account/setting-dialogs/change-password/main-dialog";
import SessionManager from "@/features/account/settings/security/components/session-manager";
import { ROUTES } from "@/lib/utils/api/endpoints";
import { serverGet } from "@/lib/utils/api/server-fetch";

export default async function Page() {
const activeSessions = await serverGet(ROUTES.account.getActiveSessions);

export default function Page() {
return (
<div className="flex flex-col gap-6">
<div className="bg-panel flex flex-col gap-4 rounded-3xl border-none p-6 md:p-8">
Expand All @@ -17,6 +20,8 @@ export default function Page() {
<ChangePasswordDialog />
</div>
</div>

<SessionManager sessions={activeSessions} />
</div>
);
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,302 @@
"use client";

import {
startTransition,
useEffect,
useOptimistic,
useRef,
useState,
} from "react";

import * as Collapsible from "@radix-ui/react-collapsible";
import { toZonedTime } from "date-fns-tz";
import {
ChevronDownIcon,
CircleQuestionMark,
Laptop2Icon,
SmartphoneIcon,
TabletIcon,
} from "lucide-react";

import { pruneSessions } from "@/features/account/settings/security/prune-sessions";
import { removeSession } from "@/features/account/settings/security/remove-session";
import ActionButton from "@/features/button/components/action";
import { ConfirmationDialog, useToast } from "@/features/system-feedback";
import { MESSAGES } from "@/lib/messages";
import { ActiveSessionList, type ActiveSession } from "@/lib/utils/api/types";
import { cn } from "@/lib/utils/classname";
import { formatTimeAgo } from "@/lib/utils/date-time-format";

type SessionAction = { type: "remove"; publicId: string } | { type: "prune" };

export default function SessionManager({
sessions,
}: {
sessions: ActiveSessionList;
}) {
const [now, setNow] = useState(Date.now());
// This updates the "last used" timestamps every minute
useEffect(() => {
const interval = setInterval(() => {
setNow(Date.now());
}, 60000); // Update every minute
return () => clearInterval(interval);
}, []);

const userTimeZone = Intl.DateTimeFormat().resolvedOptions().timeZone;

const [optimisticSessions, setOptimisticSessions] = useOptimistic(
sessions,
(state, action: SessionAction) => {
switch (action.type) {
case "remove":
return {
current_session: state.current_session,
other_sessions: state.other_sessions.filter(
(s) => s.public_id !== action.publicId,
),
};
case "prune":
return {
current_session: state.current_session,
other_sessions: [],
};
default:
return state;
}
},
);

const [pruneConfirmationOpen, setPruneConfirmationOpen] = useState(false);
const [removeConfirmationOpen, setRemoveConfirmationOpen] = useState(false);
const sessionToRemove = useRef<string | null>(null);
const { addToast } = useToast();

const handlePruneSessions = async () => {
// Immediate UI update
startTransition(() => {
setOptimisticSessions({ type: "prune" });
});

// Server Action
const result = await pruneSessions();

if (!result.success) {
addToast("error", result.error || MESSAGES.ERROR_GENERIC);
} else {
addToast("success", MESSAGES.SUCCESS_SESSION_PRUNE);
}
};

const handleRemoveSession = async (publicId: string) => {
// Immediate UI update
startTransition(() => {
setOptimisticSessions({ type: "remove", publicId });
});

// Server Action
const result = await removeSession(publicId);

if (!result.success) {
addToast("error", result.error || MESSAGES.ERROR_GENERIC);
} else {
addToast("success", MESSAGES.SUCCESS_SESSION_REMOVE);
}
};
Comment on lines +75 to +105

@coderabbitai coderabbitai Bot Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n -C 12 \
  'startTransition|setOptimisticSessions|await pruneSessions|await removeSession' \
  frontend/src/features/account/settings/security/components/session-manager.tsx

Repository: plan-cake/plancake

Length of output: 2744


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '%s\n' '--- component structure and timestamp parsing ---'
sed -n '1,230p' frontend/src/features/account/settings/security/components/session-manager.tsx

printf '%s\n' '--- React and Next versions ---'
rg -n '"react"|"next"' frontend/package.json package.json 2>/dev/null || true

printf '%s\n' '--- session-manager callers and session data declarations ---'
rg -n -C 8 'SessionManager|interface Session|type Session|last_used|last_active|created_at' frontend/src/features/account frontend/src 2>/dev/null | head -n 240

Repository: plan-cake/plancake

Length of output: 21504


🌐 Web query:

React useOptimistic startTransition async action optimistic state pending official documentation

💡 Result:

According to the official React documentation, the useOptimistic hook is designed to show a temporary state while an asynchronous Action is in progress [1][2]. It works by returning an optimistic value that is rendered while a Transition is active [3]. To use useOptimistic with an async action: 1. Call the setter function returned by useOptimistic (often named something like addOptimistic or setOptimistic) inside a Transition [1][4]. 2. A Transition is created by wrapping the update in startTransition or by using a form Action [1][5]. 3. When the setter is called inside this Transition, React immediately re-renders the UI to display the optimistic state [2][3]. 4. The Transition remains "pending" until the async action (e.g., a network request) completes [5][3]. 5. Once the action settles, React automatically reconciles the state. If the parent state updates, the optimistic layer is discarded; if the action fails or the state does not change, the optimistic state is dropped, and the UI reverts to the last confirmed state [3]. Crucially, you must call the optimistic setter function inside a transition [1][4]. If you call it outside of one, React will issue a warning, and the optimistic state will not persist correctly [1][2][4]. When performing async work inside startTransition, ensure any state updates scheduled after an await are wrapped in their own startTransition, as this is currently required by React to ensure they are treated as part of the Transition [6][5][7]. For tracking whether the transition is ongoing, you can use the isPending boolean provided by the useTransition hook, which remains true from the start of the transition until all associated actions are completed [5][2][7]. Top results: [1], [6], [5], [4], [3]

Citations:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '%s\n' '--- session API and serializer definitions ---'
rg -n -C 12 \
  'ActiveSession|active.?sessions|last_used|created_at|DateTimeField|SessionSerializer' \
  --glob '!frontend/src/features/account/settings/security/components/session-manager.tsx' \
  --glob '!**/node_modules/**' . | head -n 320

printf '%s\n' '--- mutation implementations and refresh behavior ---'
sed -n '1,220p' frontend/src/features/account/settings/security/prune-sessions.ts
sed -n '1,220p' frontend/src/features/account/settings/security/remove-session.ts
rg -n -C 8 'revalidatePath|router.refresh|refresh\(' frontend/src/features/account/settings/security frontend/src | head -n 240

printf '%s\n' '--- deterministic source checks ---'
python3 - <<'PY'
from pathlib import Path
import re

p = Path("frontend/src/features/account/settings/security/components/session-manager.tsx")
s = p.read_text()

for name, pattern in {
    "prune optimistic transition": r"startTransition\(\(\) => \{\s*setOptimisticSessions\(\{ type: \"prune\" \}\);\s*\}\);\s*.*?await pruneSessions\(\)",
    "remove optimistic transition": r"startTransition\(\(\) => \{\s*setOptimisticSessions\(\{ type: \"remove\", publicId \}\);\s*\}\);\s*.*?await removeSession\(publicId\)",
    "last_used parser": r"new Date\(session\.last_used \+ \"Z\"\)",
    "created_at parser": r"new Date\(session\.created_at \+ \"Z\"\)",
}.items():
    print(f"{name}: {bool(re.search(pattern, s, re.S))}")

for field in ("last_used", "created_at"):
    print(f"{field} + Z parses:")
    for value in ("2026-08-01T12:34:56Z", "2026-08-01T12:34:56.123Z", "2026-08-01T12:34:56"):
        candidate = value + "Z"
        # ECMAScript Date parsing is checked as data here; report the resulting
        # ISO value where Python can parse the equivalent forms.
        valid = not bool(re.search(r"ZZ$", candidate))
        print(f"  {value!r} -> {candidate!r}; syntactic double-Z: {not valid}")
PY

Repository: plan-cake/plancake

Length of output: 43277


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '%s\n' '--- backend file inventory for session code ---'
git ls-files | rg -i 'session|serializer|account' | head -n 240

printf '%s\n' '--- exact session endpoint references ---'
rg -n -C 20 \
  'active-sessions|terminate-session|prune-sessions|UserSession|user_session' \
  backend frontend --glob '!**/node_modules/**' | head -n 400

printf '%s\n' '--- Django datetime configuration and field definitions ---'
rg -n -C 8 \
  'DateTimeField|DateTimeNoTZField|USE_TZ|DATETIME_FORMAT|REST_FRAMEWORK|created_at|last_used' \
  backend --glob '*.py' | head -n 400

Repository: plan-cake/plancake

Length of output: 50374


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '%s\n' '--- backend account serializers ---'
cat -n backend/api/account/serializers.py

printf '%s\n' '--- backend account views: session endpoints ---'
rg -n -C 35 \
  'def get_active_sessions|def terminate_session|def prune_sessions' \
  backend/api/account/views.py

printf '%s\n' '--- custom datetime field ---'
sed -n '1,35p' backend/api/models.py

Repository: plan-cake/plancake

Length of output: 9016


🌐 Web query:

Django REST framework DateTimeField ISO-8601 representation naive datetime USE_TZ False trailing Z official documentation source

💡 Result:

In Django REST framework, the ISO-8601 representation of a DateTimeField is controlled by the to_representation method [1][2]. When the field's format is set to 'iso-8601' (which is the default) [3][4], the DRF implementation converts the datetime object to an ISO-8601 string [1][2]. Regarding the trailing 'Z': 1. The underlying implementation of to_representation uses Python's datetime.isoformat() [1][2]. 2. If the datetime is UTC aware, isoformat() may return a string ending in +00:00. 3. To ensure a standard ISO-8601 representation, DRF explicitly checks for this and replaces the +00:00 suffix with Z [5][1][2]. When USE_TZ is set to False in your Django settings, the DateTimeField default behavior is to treat datetime objects as naive [3][6]. The field's enforce_timezone method ensures that when USE_TZ is False, the default timezone is None, resulting in naive datetimes being returned or processed [7][5]. Because these objects are naive, they do not have an offset, and consequently, the to_representation logic—which specifically targets +00:00 for the Z replacement—will not append Z to the output unless the object is explicitly made aware and set to UTC [1][2]. In summary, when USE_TZ is False, your datetimes are naive and will be rendered by isoformat() without a timezone suffix, meaning no trailing Z will be added by the framework [1][2].

Citations:


Keep each server mutation inside its transition.

The current synchronous transitions finish before pruneSessions() and removeSession() start. Wrap each mutation in an async startTransition callback so the optimistic state remains active until the mutation completes.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coderabbitai Could you clarify what you mean by this? This is the same logic flow we use in other areas of the site and it has no problem with everything functioning as intented. Unless, are we missing something and our optimistic transitions actually aren't working properly?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '%s\n' '--- React versions ---'
rg -n -C 2 '"react"|"react-dom"|next' frontend/package.json package.json 2>/dev/null || true

printf '%s\n' '--- session manager relevant sections ---'
sed -n '32,135p' frontend/src/features/account/settings/security/components/session-manager.tsx

printf '%s\n' '--- useOptimistic usage with transitions and mutations ---'
rg -n -U -C 10 \
  'useOptimistic[\s\S]{0,220}startTransition|startTransition[\s\S]{0,220}(useOptimistic|await )' \
  frontend/src --glob '*.{ts,tsx}' || true

printf '%s\n' '--- direct optimistic setter and async server-action patterns ---'
rg -n -C 8 \
  'setOptimistic|addOptimistic|startTransition\s*\(\s*(async|\(\)\s*=>)' \
  frontend/src --glob '*.{ts,tsx}' || true

Length of output: 25552


@jzgom067, the current code does render the optimistic update. The problem is its lifetime.

setOptimisticSessions() runs inside this synchronous transition:

startTransition(() => {
  setOptimisticSessions({ type: "prune" });
});

That transition completes when the callback returns. pruneSessions() starts after the transition has completed. React therefore does not associate the pending server action with the optimistic update.

As a result, the UI can show the removed session immediately, but React does not guarantee that the optimistic state remains active until pruneSessions() or removeSession() completes. If the confirmed sessions prop has not updated yet, React can revert to that base state before the request completes. The server action’s revalidatePath() can then update the UI again after success. Fast requests can make this sequence appear correct in normal use.

The dashboard and event-results code use the same pattern. This is a shared limitation, not evidence that this implementation is different.

For React 19, the transition should include both the optimistic update and the server mutation:

startTransition(async () => {
  setOptimisticSessions({ type: "prune" });

  const result = await pruneSessions();

  if (!result.success) {
    addToast("error", result.error || MESSAGES.ERROR_GENERIC);
  } else {
    addToast("success", MESSAGES.SUCCESS_SESSION_PRUNE);
  }
});

The same structure applies to removeSession().

I should have stated the concern more precisely. This is not a claim that the current UI always fails. It is a claim that the optimistic state is not tied to the pending mutation, so it is not reliable under latency or delayed revalidation.

You are interacting with an AI system.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coderabbitai I'm still not understanding. Isn't the point of the optimistic state to activate early, and stay active until revalidatePath is called?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jzgom067, no. I described that relationship incorrectly in the earlier reply.

revalidatePath() does not keep useOptimistic state active.

revalidatePath() runs on the server. It invalidates the cached route data. Next.js later sends updated route data to the client.

useOptimistic is controlled by React on the client. React keeps its optimistic state for the Transition that contains setOptimisticSessions().

The current code does this:

  1. Start a Transition.
  2. Call setOptimisticSessions().
  3. End the Transition.
  4. Call pruneSessions() or removeSession().
  5. The server action calls revalidatePath().

Therefore, the optimistic state is not tied to Step 4 or Step 5.

The UI can still appear correct because the optimistic update renders immediately, and the server action usually returns quickly with refreshed data. However, revalidatePath() is not the mechanism that preserves the optimistic state during that interval.

The intended React 19 pattern is to put the server action in the same asynchronous Transition:

startTransition(async () => {
  setOptimisticSessions({ type: "prune" });

  const result = await pruneSessions();

  if (!result.success) {
    addToast("error", result.error || MESSAGES.ERROR_GENERIC);
  } else {
    addToast("success", MESSAGES.SUCCESS_SESSION_PRUNE);
  }
});

This makes the optimistic update and the pending server action one Transition. The same change applies to handleRemoveSession().

You are interacting with an AI system.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coderabbitai I'm talking with someone else, and they are explaining to me that keeping my code as is, only using startTransition for the optimistic state update is the correct way. This way, the server action isn't blocking the transition from finishing. The optimistic state is handled via useOptimistic on its own, it doesn't depend on startTransition. Am I still misunderstanding?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jzgom067, the other explanation is correct about one important part: an async startTransition() does not block the UI while the server action runs.

However, useOptimistic does depend on an Action or Transition for its optimistic state lifetime. React requires setOptimisticSessions() to run inside a Transition or Action. When the Transition ends, React can discard the optimistic layer unless a pending Action still owns it.

Your current sequence is:

  1. Start a synchronous Transition.
  2. Call setOptimisticSessions().
  3. End the Transition.
  4. Start pruneSessions() or removeSession() outside the Transition.

This does render the optimistic UI immediately. The concern is that Step 3 occurs before the server action starts. React does not associate the pending server action with that optimistic update.

An async Transition has the required behavior without blocking the interface:

startTransition(async () => {
  setOptimisticSessions({ type: "prune" });

  const result = await pruneSessions();

  if (!result.success) {
    addToast("error", result.error || MESSAGES.ERROR_GENERIC);
  } else {
    addToast("success", MESSAGES.SUCCESS_SESSION_PRUNE);
  }
});

The UI stays responsive. React marks the Transition as pending while pruneSessions() runs. useOptimistic can then retain the optimistic state until the action settles and the refreshed server data becomes available.

So, you are not misunderstanding the goal of optimistic UI. The disputed point is the Transition scope. Keeping only the optimistic setter in a synchronous Transition can appear to work for fast actions, but it does not connect the optimistic state to the server action. The async Transition is the React-supported pattern for this case.

You are interacting with an AI system.


const onRemoveSession = (publicId: string) => {
sessionToRemove.current = publicId;
setRemoveConfirmationOpen(true);
};

return (
<div className="bg-panel flex flex-col gap-4 rounded-3xl border-none p-6 md:p-8">
<div>
<h2 className="text-lg font-bold">Active Sessions</h2>
<p className="mt-1 text-sm leading-tight opacity-75">
These devices have access to your account. If there are any you don
{"'"}t recognize, remove them and change your password.
</p>
</div>

<Session
session={optimisticSessions.current_session}
now={now}
userTz={userTimeZone}
/>
<div className="bg-foreground/10 h-px w-full" />
{optimisticSessions.other_sessions.length > 0 ? (
<>
<div className="flex flex-col gap-2">
{optimisticSessions.other_sessions.map((session) => (
<Session
key={session.public_id}
session={session}
now={now}
userTz={userTimeZone}
onRemove={() => {
onRemoveSession(session.public_id);
}}
/>
))}
</div>

<ActionButton
buttonStyle="danger"
label="Remove All Other Sessions"
className="mx-auto w-fit"
onClick={() => {
setPruneConfirmationOpen(true);
}}
/>
</>
) : (
<p className="text-center text-sm opacity-75">
No other active sessions.
</p>
)}

<ConfirmationDialog
type="delete"
autoClose={true}
title="Remove Session"
description="Are you sure you want to log out of this device?"
open={removeConfirmationOpen}
onOpenChange={setRemoveConfirmationOpen}
onConfirm={() => {
if (!sessionToRemove.current) return false;
handleRemoveSession(sessionToRemove.current);
return true;
}}
/>
<ConfirmationDialog
type="delete"
autoClose={true}
title="Remove All Other Sessions"
description="Are you sure you want to log out of all other devices? You will remain logged in here."
open={pruneConfirmationOpen}
onOpenChange={setPruneConfirmationOpen}
onConfirm={() => {
handlePruneSessions();
return true;
}}
/>
</div>
);
}

function Session({
session,
now,
userTz,
onRemove,
}: {
session: ActiveSession;
now: number;
userTz: string;
onRemove?: () => void;
}) {
const [isOpen, setIsOpen] = useState(false);

const lastUsedLocal = toZonedTime(new Date(session.last_used + "Z"), userTz);
const lastUsedSecondsAgo = (now - lastUsedLocal.getTime()) / 1000;

const createdAtLocal = toZonedTime(
new Date(session.created_at + "Z"),
userTz,
);

return (
<div className="bg-background w-full rounded-3xl p-2">
<Collapsible.Root open={isOpen} onOpenChange={setIsOpen}>
<Collapsible.Trigger
className={
"group flex w-full cursor-pointer justify-between gap-2 text-left"
}
>
<div className="flex gap-2">
<div
className={cn(
"bg-panel h-fit rounded-full p-2",
session.is_current && "bg-accent/50 text-accent-text",
)}
>
{session.device_type === "desktop" ? (
<Laptop2Icon className="h-5 w-5" />
) : session.device_type === "smartphone" ? (
<SmartphoneIcon className="h-5 w-5" />
) : session.device_type === "tablet" ? (
<TabletIcon className="h-5 w-5" />
) : (
<CircleQuestionMark className="h-5 w-5" />
)}
</div>

<div className="flex flex-col items-start justify-between">
<div className="text-sm font-semibold">
{!session.os_name && !session.client_name
? "Unknown"
: (session.os_name || "Unknown Device") +
" • " +
(session.client_name || "Unknown Browser")}
</div>
<div className="text-xs opacity-75">
{session.is_current
? "This Session"
: `Last used ${formatTimeAgo(lastUsedSecondsAgo)}`}
</div>
</div>
</div>
<div
className={cn(
"group-hover:bg-accent/25 group-active:bg-accent/40",
"m-1 h-fit rounded-full p-1",
)}
>
<div
className={cn(
"transition-transform duration-200",
isOpen && "rotate-x-180",
)}
>
<ChevronDownIcon className="h-5 w-5" />
</div>
</div>
</Collapsible.Trigger>
<Collapsible.Content className="collapsible-content">
<div className="mt-2 flex flex-col gap-2 pl-2 md:flex-row md:items-end md:justify-between">
<div className="text-sm">
{session.os_name && session.os_version && (
<p>
{session.os_name} {session.os_version}
</p>
)}
{session.client_name && session.client_version && (
<p>
{session.client_name} {session.client_version}
</p>
)}
<p className="opacity-75">
Logged in on{" "}
{createdAtLocal.toLocaleString(undefined, {
month: "short",
day: "numeric",
hour: "numeric",
minute: "numeric",
})}
</p>
</div>
{onRemove && (
<ActionButton
buttonStyle="danger"
label="Remove"
className="mx-auto w-fit md:mx-0"
onClick={onRemove}
/>
)}
</div>
</Collapsible.Content>
</Collapsible.Root>
</div>
);
}
Loading
Loading