Skip to content

teams: smoother repository summary modelling (fixes #11710)#11631

Merged
dogi merged 4 commits intomasterfrom
refactor-team-summary-boundary-8006425631081337400
Mar 4, 2026
Merged

teams: smoother repository summary modelling (fixes #11710)#11631
dogi merged 4 commits intomasterfrom
refactor-team-summary-boundary-8006425631081337400

Conversation

@dogi
Copy link
Member

@dogi dogi commented Mar 2, 2026

This commit introduces a boundary-safe TeamSummary model and updates TeamsRepository to return this model alongside deprecating the direct Realm-returning method getShareableTeams(). It selectively updates ChatHistoryFragment and its associated adapters to consume the new TeamSummary data class, decoupling the presentation layer from the Realm database.


PR created automatically by Jules for task 8006425631081337400 started by @dogi

…toryFragment

- Created `TeamSummary` data class to serve as a boundary-safe POJO for `RealmMyTeam`.
- Added `getTeamSummaries()` boundary method to `TeamsRepository` and `TeamsRepositoryImpl`.
- Deprecated `getShareableTeams()` in `TeamsRepository`.
- Migrated `ChatHistoryFragment` and related components (`ChatShareTargets`, `ChatHistoryAdapter`, `TeamsSelectionAdapter`) to use `TeamSummary`.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link
Collaborator

@Okuro3499 Okuro3499 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- Extend ChatShareTargets.enterprises and .community to use TeamSummary/TeamSummary? and move the conversion to the repository (add getEnterprisesSummaries() or a unified getShareTargets() method). Remove the inline mapping from the click handler.
- Either give getTeamSummaries() its own Realm query scoped to the needed fields, or add a code comment explicitly stating that the delegation is intentional and only for type isolation.

- Refactored `ChatShareTargets` so `enterprises` and `community` use `TeamSummary`.
- Added `getShareableEnterpriseSummaries` and `getTeamSummaryById` to `TeamsRepository` and `TeamsRepositoryImpl` with explicit delegation comments.
- Removed inline mapping logic from `ChatHistoryAdapter`'s click handlers, passing `TeamSummary` models directly from the repository layer.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@dogi dogi requested a review from Okuro3499 March 3, 2026 14:58
@dogi dogi changed the title Refactor TeamsRepository to use TeamSummary boundary model in ChatHistoryFragment Refactor TeamsRepository to use TeamSummary boundary model in ChatHistoryFragment (fixes #11710) Mar 4, 2026
@dogi dogi changed the title Refactor TeamsRepository to use TeamSummary boundary model in ChatHistoryFragment (fixes #11710) teams: smoother repository summary modelling (fixes #11710) Mar 4, 2026
@dogi dogi merged commit 5590ec8 into master Mar 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants