-
Notifications
You must be signed in to change notification settings - Fork 0
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/fragment ordering tc2 #384
Conversation
@acholyn Sorry I just realised having running pre-commit and updated loads of files makes it really hard to see what's changed. Mostly models.base, models.antiquarians, models.work, and the migration file. |
@@ -773,9 +773,6 @@ def test_testimonium_queryset_methods(self): | |||
self.assertEqual(0, self.testimonium.definite_antiquarian_links().count()) | |||
self.assertEqual(1, self.testimonium.possible_antiquarian_links().count()) | |||
|
|||
@pytest.mark.skip( | |||
"This can be revisited when definite status is broken down into ant/wk/bk" | |||
) | |||
def test_add_antiquarian_fragment_ignores_work(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this test pass for you then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I had to fix a few things to do with testimonium ordering: basically put testimonia belonging to unknown works before those attached to other works (opposite to how it works for fragments and apposita)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you!
Changes include: