-
Notifications
You must be signed in to change notification settings - Fork 24
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
feat: Add unified document to feed entries #2145
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2145 +/- ##
==========================================
- Coverage 68.57% 68.46% -0.11%
==========================================
Files 428 427 -1
Lines 23011 22872 -139
==========================================
- Hits 15779 15659 -120
+ Misses 7232 7213 -19 ☔ View full report in Codecov by Sentry. |
src/feed/models.py
Outdated
ResearchhubUnifiedDocument, | ||
on_delete=models.CASCADE, | ||
null=True, | ||
blank=True, |
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.
Should we make it a non nullable field or do we want to avoid creating that sort of requirement on feed entries?
|
Add a direct relation to unified documents to feed entries.
This is primarily for performance reasons. Since different entity types managed in the feed can have their relation to the unified document on a different level, this change makes sure that we can easily join the feed with the unified document uniformly.