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
@@ -26,6 +26,7 @@ import DetailDrawer, { ObjectDetails } from "../components/DetailDrawer";
import { useRowDetail } from "../hooks/useRowDetail";
import { formatDateTime } from "../utils/date";
import ExportTableButton from "../components/ExportTableButton";
import { EmptyRow } from "../components/EmptyState";
function proxmoxStatusBadge(status: string) {
return status === "running" ? (
@@ -590,11 +591,7 @@ export default function Proxmox({ user }: { user: CurrentUser }) {
</tr>
))}
{sortedGuests?.length === 0 && (
<tr>
<td colSpan={canEdit ? 6 : 5} className="text-secondary text-center">
No VMs or containers found across any node.
</td>
</tr>
<EmptyRow colSpan={canEdit ? 6 : 5} title="No guests found" hint="The cluster answered with no virtual machines or containers. Check that the API token can see them." action={{ label: "Check the integration", to: "/integrations" }} filtered={tableSearch.active ? () => tableSearch.setQuery("") : undefined} />
)}
</tbody>
</table>