feat(llc): add teams to user#124
Conversation
|
Warning Review limit reached
Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesUser teams field
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 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 |
Codecov Report❌ Patch coverage is
❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #124 +/- ##
=======================================
Coverage 37.26% 37.26%
=======================================
Files 175 175
Lines 6986 6986
=======================================
Hits 2603 2603
Misses 4383 4383 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/stream_core/lib/src/user/user.dart`:
- Around line 19-20: The User value object is storing a caller-provided teams
list that can still be mutated after construction, which can break
Equatable-based equality and lookups; update the User constructor and any
related copy/serialization paths in user.dart so teams is defensively copied
into an immutable collection before assignment, and keep the User/teams handling
consistent wherever the field is created or compared.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1cc7e15d-ba50-42ae-811d-0e081fa1dd90
📒 Files selected for processing (2)
packages/stream_core/CHANGELOG.mdpackages/stream_core/lib/src/user/user.dart
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/stream_core/lib/src/user/user.dart`:
- Around line 23-31: `User.guest` in the `User` class has been changed from a
const-compatible API to a factory, which breaks existing `const User.guest(...)`
call sites. Update the `User.guest` constructor to remain const-compatible by
using a delegating const constructor pattern inside `User`, while still
supporting the optional `name` parameter and preserving the existing
`User.guest` symbol for callers.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 0b8bbc52-1809-4d2e-884f-306d14cbac07
📒 Files selected for processing (1)
packages/stream_core/lib/src/user/user.dart
Summary by CodeRabbit
teamsfield.User.guestnow accepts an optional display name (User.guest(userId, {name})) instead of always using theuserIdas the name.