Skip to content

#950: compare assessments by their earliest timestamp value - #953

Open
gemshrine wants to merge 6 commits into
zerocracy:masterfrom
gemshrine:950
Open

gemshrine wants to merge 6 commits into
zerocracy:masterfrom
gemshrine:950

Conversation

@gemshrine

@gemshrine gemshrine commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

The judge used Fact#when both to compare assessments and to populate the summary. That accessor exposes only the first value of a multi-valued property, while the page's z:when helper defines the effective timestamp as the earliest value. The summary could therefore select an assessment that is not actually latest.

The judge now compares assessments by the minimum value in each when property and stores that same effective timestamp.

Checks: the regression case in TestLatestAssessment#test_uses_earliest_value_when_comparing_multi_valued_dates and the repository's Ruby CI suite.

Closes #950

@gemshrine

Copy link
Copy Markdown
Contributor Author

@yegor256 Could you review this fix for #950?

@gemshrine

Copy link
Copy Markdown
Contributor Author

@yegor256 I merged the current master and kept the earliest-timestamp comparison. All required CI checks are green.

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.

latest-assessment judge incorrectly chooses fact with earliest when value among multiple

1 participant