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
@@ -15,6 +15,7 @@ import { downloadCsv } from "../utils/csv";
import IntegrationPageTitle from "../components/IntegrationPageTitle";
import { ErrorNotice } from "../components/Notice";
import ExportTableButton from "../components/ExportTableButton";
import { EmptyRow } from "../components/EmptyState";
function formatBytes(bytes: number | null): string {
if (bytes === null) return "—";
@@ -282,11 +283,7 @@ export default function PbsBackup({ user: _user }: { user: CurrentUser }) {
</tr>
))}
{sortedDatastores?.length === 0 && (
<tr>
<td colSpan={5} className="text-secondary text-center">
No datastores found.
</td>
</tr>
<EmptyRow colSpan={5} title="No datastores found" hint="The Backup Server answered but listed none. Check that the API token has access to a datastore." action={{ label: "Check the integration", to: "/integrations" }} />
)}
</tbody>
</table>