Changed settings to use local error boundary - #29379
Conversation
no ref The settings app already owns the shared error-boundary behavior, so keeping a duplicate design-system HOC left an unnecessary legacy dependency.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThe design system removes the Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx run @tryghost/admin-x-settings:test:acceptance |
✅ Succeeded | 7m 4s | View ↗ |
nx run @tryghost/admin:test:acceptance |
✅ Succeeded | 2m 46s | View ↗ |
nx run-many -t test:unit -p @tryghost/admin-x-d... |
✅ Succeeded | 2m 23s | View ↗ |
nx run ghost-monorepo:lint:boundaries |
✅ Succeeded | 20s | View ↗ |
nx run-many -t lint -p @tryghost/admin-x-design... |
✅ Succeeded | 1m 14s | View ↗ |
nx run @tryghost/admin:build |
✅ Succeeded | 37s | View ↗ |
nx run-many --target=build --projects=tag:publi... |
✅ Succeeded | <1s | View ↗ |
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗
☁️ Nx Cloud last updated this comment at 2026-07-16 12:50:17 UTC

What changed
withErrorBoundaryconsumer to the existing app-local implementation.ErrorBoundaryandErrorBoundaryPropsbecause Koenig still uses the component internally.Why
admin-x-settings already owns the identical error-boundary behavior. Removing the final legacy HOC dependency reduces the admin-x-design-system surface while preserving runtime behavior.
Validation
git diff --checkManual testing