fix(web): defuse date time bomb in push-relay admin settings test (#589)
The fixture hardcoded push_relay_expires_at as 2026-08-10, so once the calendar reached that date the component rendered the "Expired" branch and the "renews automatically" assertion failed on every branch's CI. Use a relative +30d expiration so the not-yet-expired branch stays stable. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -36,7 +36,10 @@ function makeForm() {
|
||||
case "notifications.push_relay_key_prefix":
|
||||
return "cap_v1_test";
|
||||
case "notifications.push_relay_expires_at":
|
||||
return "2026-08-10T00:00:00Z";
|
||||
// Relative so the "renews automatically" (not-yet-expired) branch
|
||||
// stays stable — a hardcoded date turned into a time bomb once the
|
||||
// calendar passed it.
|
||||
return new Date(Date.now() + 30 * 24 * 60 * 60 * 1000).toISOString();
|
||||
default:
|
||||
return "";
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user