Remove parser test fixtures that nothing references - #6675
Conversation
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
SDK Size Comparison 📏
|
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
💤 Files with no reviewable changes (8)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. WalkthroughThe change deletes eight parser2 test fixture files. The removed fixtures contained JSON payloads and expected model objects for parser tests. Changes
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change removes unused test-only fixtures without changing production behavior; no actionable merge-blocking risk remains. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description includes the goal, implementation details, linked issue, and testing rationale. It identifies all eight deleted fixtures and explains why no production or referenced test changes are required. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. ✨ 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 |
|
🚀 Available in v7.11.0 |



Goal
Remove eight fixture objects in
parser2/testdatathat nothing references.They were added by #6473 alongside the fixtures the fast event parsing path does use, but they describe types with no adapter in
parser2/direct, and no such adapter has ever existed, so nothing could consume them. They have since drifted, still assertinginvisible = falsefor nested users where the wire never sends the field.Closes AND-1469
Implementation
AnswerTestData,ChannelTestData,ChannelUserReadTestData,CommandTestData,ConfigTestData,MemberTestData,PushPreferenceTestDataandVoteTestData.Testing
DtoTestDataTestalso has no references, being a test class the runner executes, and it names its fixtures explicitly. None of the removed objects appear there, so it keeps compiling and passing.Summary by CodeRabbit