You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(notifications): gate IU in-product too + resilient settings fetch
Two follow-ups on OUT-3929:
1. Gate the in-product surface as well (per updated requirement). The
notificationSettingId is now attached to the immediate in-product IU dispatch
in create()/createBulkNotification, not just the buffered email, so the
platform gates both surfaces against the IU's preference. We don't gate
ourselves; we just pass the id.
2. Address Greptile review:
- P1: resolveTasksNotificationSettingId catches getNotificationSettings
failures and returns undefined instead of throwing. A failure no longer
skips buffering + the in-product dispatch (which silently dropped the whole
notification). Undefined id = platform delivers all (fail-open); the failure
is not cached so the next send retries. With in-product now gated too,
fail-open is the coherent choice - failing closed would mean dropping the
entire notification during a settings-API outage.
- P2: drop redundant `?? undefined` after `.find(Boolean)` in the flush.
- P2: add the standard console.info trace to _getNotificationSettings.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments