From c16407cf4bb3f1038e31912fca1065ad66640071 Mon Sep 17 00:00:00 2001 From: Marcin Rataj Date: Thu, 26 Feb 2026 02:19:28 +0100 Subject: [PATCH 1/2] fix: remove incorrect max-validity constraint on lifetime input closes #26 - components/ipns-inspector.tsx: remove MAX_VALIDITY (was 1 year in seconds) used as max on a milliseconds input, causing browser validation error even for the "1 day" preset - lib/ipns-machine.tsx: fix misleading comment ("in seconds" -> "in milliseconds") --- components/ipns-inspector.tsx | 2 -- lib/ipns-machine.tsx | 2 +- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/components/ipns-inspector.tsx b/components/ipns-inspector.tsx index 511e5f2..eba8d88 100644 --- a/components/ipns-inspector.tsx +++ b/components/ipns-inspector.tsx @@ -23,7 +23,6 @@ import { DialogTrigger, } from './ui/dialog' -const MAX_VALIDITY = 365 * 24 * 60 * 60 // 1 year in seconds const DAY_MS = 24 * 60 * 60 * 1000 export const NAME_VALIDATION_ERROR = 'IPNS names must be base36 encoded CIDs or base58 encoded libp2p PeerIDs' @@ -289,7 +288,6 @@ export default function IPNSInspector() { value={state.context.formData.lifetime} onChange={(e) => send({ type: 'UPDATE_FORM', field: 'lifetime', value: e.target.value })} min="1" - max={MAX_VALIDITY} />