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: Honor explicitly set default value #271

Merged
merged 2 commits into from
Dec 19, 2024

Conversation

keelerm84
Copy link
Member

When evaluating flags, the test harness has relied on the
inferDefaultFromFlag to replace an explicitly null value with an
inferred default value of the correct type.

This kind of magic only leads to confusion (hence this PR), and isn't
necessary. SDKs should be able to handle a null default as well as any
other type.

When evaluating flags, the test harness has relied on the
[`inferDefaultFromFlag`][1] to replace an explicitly null value with an
inferred default value of the correct type.

This kind of magic only leads to confusion (hence this PR), and isn't
necessary. SDKs should be able to handle a null default as well as any
other type.

[1]: https://github.com/launchdarkly/sdk-test-harness/blob/cb433a1206c5190796c021605c401b5cbaf5799c/sdktests/helpers.go#L137
@keelerm84 keelerm84 requested a review from a team as a code owner December 18, 2024 19:43
Base automatically changed from mk/sdk-1014/stablize-tests to feat/fdv2 December 19, 2024 18:21
@keelerm84 keelerm84 merged commit 14c03e2 into feat/fdv2 Dec 19, 2024
2 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-1015/fix-prereq-tests branch December 19, 2024 18:21
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