feat(settings): gate custom images with feature flag#3414
Conversation
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
|
Reviews (1): Last reviewed commit: "feat(settings): gate custom images with ..." | Re-trigger Greptile |
4e8dd43 to
0da5856
Compare
New commits pushed (delta classified non_trivial_delta) — stamphog approval dismissed; re-review running automatically.
There was a problem hiding this comment.
Small additive change gating a query behind a feature flag. The previously flagged data-loss risk (flag returning false during load causing image deletion) was addressed: customImagesEnabled now requires both the flag and data, while customImagesDisabled remains tied to an explicit server error — so no silent image removal on cold load.
|
Retaining stamphog approval — delta since last review classified as |
Generated-By: PostHog Code Task-Id: bf2043a7-7d19-4dac-9d50-c0f1780de97a fix(settings): preserve custom image while flags load Generated-By: PostHog Code Task-Id: bf2043a7-7d19-4dac-9d50-c0f1780de97a test(harness): avoid OAuth callback port collisions Generated-By: PostHog Code Task-Id: bf2043a7-7d19-4dac-9d50-c0f1780de97a
02b0b4d to
49036ff
Compare
New commits pushed (delta classified non_linear_history) — stamphog approval dismissed; re-review running automatically.
Problem
Custom sandbox image controls are discovered only through the API response. PostHog Code should use the existing rollout flag directly so the settings and task UI expose custom images only to enabled users