Lifecycle planning, and consistent empty and loading states

- Inventory: end of support and replacement cost per asset; a Lifecycle page showing what ages out year by year and what replacing it will cost; support ending within 90 days in the weekly digest
- Lists: a shared empty state saying what is missing, why, and the one thing to do; "nothing matches" with a clear button; skeleton rows instead of empty-looking lists while loading

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-18 23:18:42 +02:00
1 parent 92726568b7
commit 846af02851
50 files changed
+4434 -233

No files matched your search

+2 -5
View File
@@ -13,6 +13,7 @@ import { SearchBox } from "../components/TableToolbar";
import { useTableSearch } from "../hooks/useTableSearch";
import DetailDrawer, { ObjectDetails } from "../components/DetailDrawer";
import { useRowDetail } from "../hooks/useRowDetail";
import { EmptyRow } from "../components/EmptyState";
function statusBadge(monitor: UptimeKumaMonitor) {
switch (monitor.status) {
@@ -203,11 +204,7 @@ export default function UptimeKuma({ user: _user }: { user: CurrentUser }) {
</tr>
))}
{sorted?.length === 0 && (
<tr>
<td colSpan={7} className="text-secondary text-center">
No monitors reported by this Uptime Kuma instance.
</td>
</tr>
<EmptyRow colSpan={7} title="No monitors" hint="Add monitors in Uptime Kuma and they appear here, with the server each one watches." filtered={tableSearch.active ? () => tableSearch.setQuery("") : undefined} />
)}
</tbody>
</table>