Skip to content

feat!: Make EvaluationDetail.is_default_value a property - #555

Merged
keelerm84 merged 2 commits into
feat/10.xfrom
mk/SDK-65/is-default-value-property
Nov 3, 2026
Merged

keelerm84 merged 2 commits into
feat/10.xfrom
mk/SDK-65/is-default-value-property

Conversation

@keelerm84

@keelerm84 keelerm84 commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Summary

EvaluationDetail.is_default_value is now a property, like the other getters on EvaluationDetail. Callers must drop the parentheses and write detail.is_default_value.


Note

Overview
Breaking change: EvaluationDetail.is_default_value is now a property (like value, variation_index, and reason), not a method. Call sites must use detail.is_default_value instead of detail.is_default_value().

The sync and async clients’ default-value handling and the affected tests were updated to match. Behavior is unchanged—it still means the evaluation returned the caller’s default (variation_index is None).

Reviewed by Cursor Bugbot for commit 7f5d936. Bugbot is set up for automated code reviews on this repo. Configure here.

EvaluationDetail.is_default_value is now a property, like the other getters on EvaluationDetail. Callers must drop the parentheses and write detail.is_default_value.
@keelerm84
keelerm84 requested a review from a team as a code owner November 2, 2026 16:51

@kinyoklion kinyoklion left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We should probably change the assertions to not use bare truthiness, because methods would also have passed a truthiness test.

A bound method is truthy, so a bare truthiness assertion also passes if
is_default_value is a method. Comparing with True confirms that it is a
property that returns a bool.
@keelerm84
keelerm84 merged commit 6563735 into feat/10.x Nov 3, 2026
16 checks passed
@keelerm84
keelerm84 deleted the mk/SDK-65/is-default-value-property branch November 3, 2026 13:56
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