fix: remove non-functional ABv1 deprecation banner/dialog [ACTION-5011] - #1294
Merged
Conversation
BuilderDeprecationBanner and BuilderRemigrationWarningDialog could never reliably gate on beforeDeprecationCutoffAbv2/afterDeprecationCutoffAbv2: this app has no Statsig client, and the LaunchDarkly change listener only reacts to flag changes after the client is already running, never the initial evaluation on page load. The equivalent warning now lives on the AI Studio Agent Builder entry page in fs.action-ai instead, where it resolves through that app's working feature-flag provider. Removes the two Vue components, their usage/computed state in BuilderApp.vue, and the now-unused banner background asset. Leaves the beforeDeprecationCutoffAbv2/afterDeprecationCutoffAbv2 flag registration in serve.py's lifespan untouched, along with the generic LaunchDarklyClient/launchdarkly_client.py infra, in case something else comes to depend on it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
📝 WalkthroughWalkthroughThe Builder no longer renders deprecation or remigration warning UI. Associated components, imports, persistence and query-parameter handling, lifecycle logic, and banner styling were removed. ChangesBuilder deprecation removal
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
BuilderDeprecationBannerandBuilderRemigrationWarningDialogcould never reliably gate onbeforeDeprecationCutoffAbv2/afterDeprecationCutoffAbv2: this app has no Statsig client, andlaunchDarklyClient.ts'ssetupFlagChangeListeneronly reacts to flag changes after the client is already running via the LD JS SDK's"change"event — never the initial evaluation on page load. This banner never actually worked, so removing it is a pure cleanup with no functional loss.ACTION-5011
Changes
BuilderDeprecationBanner.vue,BuilderRemigrationWarningDialog.vue, and the unused banner background assetisPreCutoffFlagEnabled,showDeprecationBanner,showRemigrationWarningDialog, dismiss/query-param handling) fromBuilderApp.vuebeforeDeprecationCutoffAbv2/afterDeprecationCutoffAbv2registration inserve.py's lifespan, and the genericLaunchDarklyClient/launchdarkly_client.pyinfra, untouchedScreenshots
N/A — removes non-functional UI; nothing renders differently for a working session