Skip to content
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

Merged
merged 8 commits into from
Mar 4, 2025
Merged

Conversation

gzurowski
Copy link
Member

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.

@gzurowski gzurowski requested a review from a team as a code owner February 28, 2025 10:57
Copy link

codecov bot commented Feb 28, 2025

Codecov Report

Attention: Patch coverage is 85.71429% with 2 lines in your changes missing coverage. Please review.

Project coverage is 68.46%. Comparing base (ff72951) to head (93c3110).
Report is 17 commits behind head on master.

Files with missing lines Patch % Lines
src/feed/tasks.py 83.33% 2 Missing ⚠️
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.
📢 Have feedback on the report? Share it here.

ResearchhubUnifiedDocument,
on_delete=models.CASCADE,
null=True,
blank=True,
Copy link
Contributor

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?

@koutst koutst mentioned this pull request Mar 4, 2025
Copy link

sonarqubecloud bot commented Mar 4, 2025

@gzurowski gzurowski merged commit fc64c64 into master Mar 4, 2025
4 of 5 checks passed
@gzurowski gzurowski deleted the feed-unified-doc branch March 4, 2025 14:54
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