You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor(mobile): group native chat message presentation - #34424
Mobile native-chat message presentation is spread across the session directory. Group its 23 implementation and test files under the existing transcript owner, update callers and mocks, and import shared types from their concrete defining modules.
Preserve rendering, send timing, draft restoration, and native/web behavior. Move the seven existing reasoning-row cases into a focused sibling suite so the relocated test stays within the file-size limit. Update the existing send-test paths in reliability policy without changing counts or rules.
Validation: normal commit hooks; 301 mobile tests across 34 suites; mobile app and test typechecks; 32 mobile-web tests; flaky-test and reliability ratchets. Independent source audits, the complete changed-file checks, hosted CI, and merge preservation checks are required before merge.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 5 remain after this review.
Walkthrough
The mobile native-chat transcript modules, session callers, test mocks, and reliability-gate entries now use the transcript paths. The change also adds a dedicated reasoning-row test suite and removes corresponding cases from the general message test. The reported runtime logic and existing test behavior remain unchanged.
Estimated code review effort
Priority: Low
Merge Risk: Minimal · up to 9d7b9
No actionable merge-blocking issue was established. The inspected session consumers and reliability check use the relocated paths.
Pre-merge checks: 3 · 1 · 1
Failed checks: 1 warning · 1 inconclusive
Check name
Status
Explanation
Resolution
Description check
The description explains the refactor and validation, but it does not follow the required template. It omits the required ELI5, What Changed, Why, Linked Issue, Visual Proof, AI Disclosure, Review, bo…
Rewrite the description using all required template headings. Add a linked issue, explain why the approach was selected, provide visual proof or state N/A with a reason, complete the Testing and Checklist sections, address AI Disclosure as …
Docstring Coverage
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within survi…
Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed checks: 3 passed
Check name
Status
Explanation
Title check
The title clearly and concisely describes the primary change: grouping native chat message presentation files under the transcript owner.
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Description check
Explanation
The description explains the refactor and validation, but it does not follow the required template. It omits the required ELI5, What Changed, Why, Linked Issue, Visual Proof, AI Disclosure, Review, boundary, Notes, and Checklist sections.
Resolution
Rewrite the description using all required template headings. Add a linked issue, explain why the approach was selected, provide visual proof or state N/A with a reason, complete the Testing and Checklist sections, address AI Disclosure as applicable, and include the required review, boundary, and Notes information.
Full details: Docstring Coverage
Explanation
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 1 functions across 50 files. (8 skipped: 2 unsupported, 6 over the file limit.)
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
Finishing Touches: 💡 1
📝 Generate docstrings: 💡
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mobile native-chat message presentation is spread across the session directory. Group its 23 implementation and test files under the existing transcript owner, update callers and mocks, and import shared types from their concrete defining modules.
Preserve rendering, send timing, draft restoration, and native/web behavior. Move the seven existing reasoning-row cases into a focused sibling suite so the relocated test stays within the file-size limit. Update the existing send-test paths in reliability policy without changing counts or rules.
Validation: normal commit hooks; 301 mobile tests across 34 suites; mobile app and test typechecks; 32 mobile-web tests; flaky-test and reliability ratchets. Independent source audits, the complete changed-file checks, hosted CI, and merge preservation checks are required before merge.