fix: Exclude ended resources from duplicate endpoint check in query - #1228
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
WalkthroughThe SQL query in ChangesDuplicate Endpoint Query Fix
Estimated code review effort: 1 (Trivial) | ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
What type of PR is this? (check all applicable)
Description
Updates the duplicate endpoint check so ended resources no longer prevent an endpoint from being recognised as already collected for the same dataset and organisation.
The check still excludes ended endpoints.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Run the focused unit test:
Expected result: the test file passes, including coverage that the Datasette query no longer filters on
r.end_datebut still filters one.end_date.No screenshots or recordings are included because this is a backend query change with no UI impact.
Added/updated tests?
[optional] Are there any post deployment tasks we need to perform?
None.
[optional] Are there any dependencies on other PRs or Work?
None.
Summary by CodeRabbit
Bug Fixes
Tests