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
- ..
- background-step.yml
- bare-event-with-settings.yml
- branches-and-ignore.yml
- call-input-type-missing.yml
- call-input-unexpected-property.yml
- call-output-value-missing.yml
- call-secret-unknown-key.yml
- caller-job-env.yml
- caller-secrets-word.yml
- concurrency-unknown.yml
- concurrency-without-group.yml
- container-unknown.yml
- credentials-unknown.yml
- defaults-run-unknown.yml
- defaults-unknown.yml
- dispatch-input-unknown-key.yml
- dispatch-unknown-key.yml
- environment-unknown.yml
- environment-without-name.yml
- g1t-not-mapping.yml
- g1t-not-under-strategy.yml
- job-id-case-duplicate.yml
- job-id-digit.yml
- job-id-dot.yml
- job-id-reserved.yml
- merge-key-list.yml
- merge-key.yml
- on-missing.yml
- permission-metadata.yml
- permission-unknown.yml
- push-branch-typo.yml
- push-inputs.yml
- push-types.yml
- root-true-key.yml
- runs-on-mapping-unknown.yml
- runs-on-missing.yml
- schedule-not-list.yml
- schedule-without-cron.yml
- service-unknown.yml
- shell-on-action-step.yml
- step-id-duplicate.yml
- step-id-invalid.yml
- step-uses-and-run.yml
- steps-mapping.yml
- strategy-unknown.yml
- unknown-event-in-list.yml
- unknown-event-in-mapping.yml
- unknown-event.yml
- unknown-job-key.yml
- unknown-root-key.yml
- unknown-step-key.yml
- uses-and-runs-on.yml
- uses-and-steps.yml
- wait-step.yml
- with-on-run-step.yml