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
- ..
- 0001_init.sql
- 0002_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql
- 0017_workspace_managed_workflows.sql
- 0018_desktop_runners.sql
- 0019_brokered_secrets.sql
- 0020_job_token_rotation.sql
- 0021_log_retention.sql
- 0022_runner_machine.sql
- 0023_actions_enabled.sql