-
Notifications
You must be signed in to change notification settings - Fork 468
chore: Create flag migration #6356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Zaimwa9 <wadii.zaim@flagsmith.com>
# Conflicts: # frontend/web/components/pages/UserPage.tsx
talissoncosta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’ve noticed some unusual behavior during the QA session and would like to clarify it before moving forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
|
V1 not requesting CR to update segment overrides |
… override The 'Enabled by default' toggle and its tooltip were incorrectly shown when editing an identity override. This was a regression introduced in PR #6356 where the CreateFeature component was extracted with isEdit hardcoded to false. When editing an identity override, isEdit should be true so that: - The toggle shows 'Enabled' instead of 'Enabled by default' - The tooltip about initial enabled state is not shown Fixes #6580 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
How did you test this code?
E2E covers regression testing on everything this affects