syntaqxEach part of a page can say it failed, in its own place: part() (lib/partial.ts, replacing f1687c9a's soft()) reads a part beside what a page is about and keeps a failure (a service that did not answer, or answered with a 5xx) as { failed: true, what } instead of throwing, so the page can tell a part that failed from one with nothing to show and put Unavailable beside it, the way a form puts an error beside its field. A refusal or a 404 is still an answer. orElse() is for a part that can quietly do without. Unavailable has a compact one-line form for a sidebar card or a count's place. Checked: apps/web tsc -b; node --test app/lib/partial.test.ts.704e654History
- ..
- about.ts
- access.ts
- account-deletion.ts
- accounts.ts
- actions.ts
- advisories.ts
- agent-sessions.ts
- agents.ts
- ai.ts
- audit.ts
- billing.ts
- chat-markdown.test.ts
- chat-markdown.ts
- chat.test.ts
- chat.ts
- checks.ts
- clients.ts
- codeowners.ts
- coding-agents.test.ts
- coding-agents.ts
- compute.ts
- connectors.test.ts
- connectors.ts
- d1.test.ts
- d1.ts
- datasets.fixtures.json
- datasets.test.ts
- datasets.ts
- deploy-keys.ts
- deployments.ts
- discovery.test.ts
- discovery.ts
- docs.ts
- events.ts
- folios-dashboard.ts
- folios-design.ts
- folios-slides.ts
- folios.fixtures.json
- folios.test.ts
- folios.ts
- github.ts
- guardrails.ts
- identity.ts
- ids.test.ts
- ids.ts
- inbox.ts
- index.ts
- instances.ts
- integrations.ts
- members.ts
- names.test.ts
- names.ts
- notify.ts
- oauth.ts
- og.ts
- packages.ts
- people.ts
- platform.ts
- privacy.ts
- projects.ts
- rate-limits.ts
- repos.ts
- result.ts
- rules.ts
- runners.ts
- scopes.ts
- search.ts
- security-suite.ts
- security.ts
- sounds.ts
- status.ts
- teams.ts
- telemetry.ts
- updates.ts
- webhooks.ts
- work.ts