Skip to content
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

refactor: LEAP-1296: remove FF_LOPS_86 feature flag #7220

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Gondragos
Copy link
Collaborator

Removed the fflag_feat_front_lops_86_datasets_storage_edit_short feature flag and its associated code logic for dataset storage editability.

Key fflag_feat_front_lops_86_datasets_storage_edit_short
Variable Name FF_LOPS_86
Ends up as 🟥 False
Description Adding the ability to toggle dataset storage editability.

Removed the `fflag_feat_front_lops_86_datasets_storage_edit_short` feature flag and its associated code logic for dataset storage editability.
Copy link

netlify bot commented Mar 13, 2025

Deploy Preview for label-studio-docs-new-theme canceled.

Name Link
🔨 Latest commit 79f2bf1
🔍 Latest deploy log https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/67d22e974ffc1100088b4061

Copy link

netlify bot commented Mar 13, 2025

Deploy Preview for heartex-docs canceled.

Name Link
🔨 Latest commit 79f2bf1
🔍 Latest deploy log https://app.netlify.com/sites/heartex-docs/deploys/67d22e97e76e4e0008f37143

@Gondragos Gondragos changed the title refactor: remove FF_LOPS_86 feature flag refactor: LEAP-1296: remove FF_LOPS_86 feature flag Mar 13, 2025
@Gondragos Gondragos requested review from hlomzik and nass600 March 13, 2025 04:05
<Elem name="text">Check your storage settings and resync to import records</Elem>
<Button
onClick={async () => {
window.open("./settings/storage");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we removing the rest of the component tree and the link to settings for any specific reason?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand the question, but here I'm removing only the part that already doesn't appear in UI with the feature flag's state we have at the end of that feature flag's lifecycle (isFF(FF_LOPS_86) === False).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants