Skip to content

Comments

fix: Delete overrides that are no longer relevant after a project is synced#544

Merged
mike-zorn merged 2 commits intolaunchdarkly:mainfrom
ajworkos:aj/541
Jun 2, 2025
Merged

fix: Delete overrides that are no longer relevant after a project is synced#544
mike-zorn merged 2 commits intolaunchdarkly:mainfrom
ajworkos:aj/541

Conversation

@ajworkos
Copy link
Contributor

@ajworkos ajworkos commented May 31, 2025

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

Related issues

#541

Describe the solution you've provided

When a project is being updated, any override that does not have a corresponding variation entry is deleted.

Describe alternatives you've considered

N/A

Additional context

See #541, when a flag is deleted in launch darkly that has been overridden locally, and the project is synced, the override remains and cannot be deleted through the CLI/REST API.

Before

Screenshare.-.2025-05-31.8_13_39.PM.mp4

After

Screenshare.-.2025-05-31.8_15_23.PM.mp4

@ajworkos ajworkos changed the title Delete overrides that are no longer relevant after a project is synced fix: Delete overrides that are no longer relevant after a project is synced May 31, 2025
Copy link

@mike-zorn mike-zorn left a comment

Choose a reason for hiding this comment

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

This is great! Thanks for the submission and for taking the time to make it such a good one.

@mike-zorn mike-zorn merged commit e47fe05 into launchdarkly:main Jun 2, 2025
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants