Skip to content

Conversation

@tssweeney
Copy link
Collaborator

Adds Evaluation library objects

@tssweeney tssweeney requested a review from a team as a code owner October 15, 2025 02:59
@codecov-commenter
Copy link

codecov-commenter commented Oct 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@tssweeney tssweeney changed the title chore(weave): Add serialization assertions for the remaining data types: Evaluation Library Types chore(weave): Add serialization assertions for the remaining data types: Evaluation Library Types (4) Oct 15, 2025
@wandbot-3000
Copy link

wandbot-3000 bot commented Oct 15, 2025

Comment on lines +272 to +274
# Sad ... equality is really a pain to assert here (and is broken)
# TODO: Write a good equality check and make it work
equality_check=lambda a, b: True,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe this should be fixed before merging

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I agree. However, I am really trying to just get the current expectations fixed so that I can modify for a customer.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe I am missing something -- isn't the assert the expectation? How can you be sure unless the test actually passes?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

oh, the equality check is just one of many assertions. we do a bunch of validation on the actual payloads as well.

Copy link
Collaborator

@andrewtruong andrewtruong left a comment

Choose a reason for hiding this comment

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

We should test the library objects individually as well as composites

Copy link
Collaborator

@andrewtruong andrewtruong left a comment

Choose a reason for hiding this comment

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

Approving despite lack of asserts :)

Base automatically changed from tim/custom_types to tim/additional_types October 15, 2025 07:56
Base automatically changed from tim/additional_types to master October 15, 2025 08:17
@tssweeney tssweeney merged commit 70df9fb into master Oct 15, 2025
109 checks passed
@tssweeney tssweeney deleted the tim/add_library_cases branch October 15, 2025 19:02
@github-actions github-actions bot locked and limited conversation to collaborators Oct 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants