Skip to content

fix: make conversation layout realization monotonic#62

Open
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
fix/monotonic-layout-loading-384248872525381554
Open

fix: make conversation layout realization monotonic#62
google-labs-jules[bot] wants to merge 1 commit into
mainfrom
fix/monotonic-layout-loading-384248872525381554

Conversation

@google-labs-jules

Copy link
Copy Markdown
Contributor

Observed problem: The layout for the active conversation root and the transcript surface was being destroyed (unloaded) when a blocking overlay (like hydration or switching) appeared.
Root cause: ChatConversationSurfaceProjectionCoordinator was mapping ShouldShow... directly to ShouldLoad.... When visibility toggled off due to an overlay, the layout was incorrectly unloaded.
Architectural safety: The fix tracks if the control has been realized (_hasLoaded...) and ensures ShouldLoad... states never regress to false once true. This strictly aligns with Uno Platform x:Load monotonic best practices and the AGENTS.md rules without modifying existing View definitions.
Verification:

  • dotnet build SalmonEgg.sln --configuration Debug
  • dotnet test tests/SalmonEgg.Presentation.Core.Tests/SalmonEgg.Presentation.Core.Tests.csproj --configuration Debug --no-restore (isolated core tests passed successfully).
    Remaining unverified GUI-only risks: ChatView.xaml binds to these properties. It relies on the UI framework cleanly preserving the visual tree when x:Load remains true while Visibility becomes Collapsed, which is standard WinUI/Uno behavior.

PR created automatically by Jules for task 384248872525381554 started by @YoungSx

Fixes an issue where `ShouldLoadActiveConversationRoot` and `ShouldLoadTranscriptSurface` would un-load when a visual blocking overlay appeared, violating Uno lifecycle rules about monotonic layout realization (`x:Load`). These properties now track if the layout has ever been shown and remain true.

Updated `ChatConversationSurfaceProjectionCoordinatorTests` and `ChatViewModelTests` to assert this correct monotonic behavior.
@vercel

vercel Bot commented Jun 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
salmonegg Ready Ready Preview, Comment Jun 28, 2026 10:59pm

@google-labs-jules

Copy link
Copy Markdown
Contributor Author

👋 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.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants