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

fix: Remove invalid conditions from persistent tests #274

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

keelerm84
Copy link
Member

No description provided.

@keelerm84 keelerm84 requested a review from a team as a code owner January 3, 2025 20:38
Comment on lines -577 to -580
h.RequireNever(t,
checkForUpdatedValue(t, client, "flag-key", context,
ldvalue.String("value"), ldvalue.String("new-value"), ldvalue.String("default")),
time.Millisecond*500, time.Millisecond*20, "flag-key was incorrectly updated")
Copy link
Member Author

Choose a reason for hiding this comment

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

The diff looks weird, but basically the first two if / else if blocks are reduced to this single check.

In FDv2, if the data system has a data source that has provided data, we never rely on the persistent store again. As a result, the "But since ..." checks weren't valid.

}
})

s.runWithEmptyStore(t, "ignores dropped flags", func(t *ldtest.T) {
Copy link
Member Author

Choose a reason for hiding this comment

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

This is redundant with the check above. Whether I delete flags or change them, it is confirming the same thing.

@keelerm84 keelerm84 merged commit 33485df into feat/fdv2 Jan 6, 2025
2 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-1022/fix-persistent-tests branch January 6, 2025 15:51
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