Skip to content

Tune persist scroll feature of BitAppShell (#9925)#9926

Merged
msynk merged 2 commits intobitfoundation:developfrom
msynk:9925-blazorui-appshellp-persistscroll-tuning
Feb 17, 2025
Merged

Tune persist scroll feature of BitAppShell (#9925)#9926
msynk merged 2 commits intobitfoundation:developfrom
msynk:9925-blazorui-appshellp-persistscroll-tuning

Conversation

@msynk
Copy link
Member

@msynk msynk commented Feb 17, 2025

closes #9925

Summary by CodeRabbit

  • New Features

    • Improved scroll behavior on navigation events ensures the page updates its scroll position correctly.
    • Demo experience now features instant scrolling for a more immediate response when elements are shown.
  • Refactor

    • Reorganized scroll management logic to provide clearer separation between navigation event handling and post-render adjustments.

@coderabbitai
Copy link

coderabbitai bot commented Feb 17, 2025

Walkthrough

The changes update the scroll behavior management within the BitAppShell component. A new private boolean flag tracks location changes and triggers scroll adjustments after render. In both C# and TypeScript files, methods have been renamed and reorganized for clarity. Specifically, scroll calls now differentiate between navigational changes and after-render updates, and the scroll animation behavior in the demo is set to be instant rather than smooth.

Changes

File(s) Change Summary
src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.razor.cs Added _locationChanged flag; updated OnAfterRenderAsync to conditionally trigger BitAppShellAfterRenderScroll; modified LocationChanged to set the flag and call BitAppShellLocationChangedScroll when PersistScroll is true.
src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.ts Reorganized scroll management; renamed navigateScroll to locationChangedScroll; updated initScroll to set _currentUrl and initialize scroll values; revised afterRenderScroll to set scroll position and add listeners after removing previous ones.
src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShellJsRuntimeExtensions.cs Renamed method BitAppShellNavigateScroll to BitAppShellLocationChangedScroll and updated its call; added new method BitAppShellAfterRenderScroll to integrate with after-render scroll handling.
src/BlazorUI/Demo/Client/…/Scripts/app.ts Modified the scrollToElement function to change the scrollIntoView behavior from "smooth" to "instant".

Sequence Diagram(s)

sequenceDiagram
    participant AppShell as BitAppShell Component
    participant NavManager as Navigation Manager
    participant JSRuntime as JS Runtime
    AppShell->>NavManager: Detect location change
    NavManager-->>AppShell: Update current URL & set _locationChanged = true
    AppShell->>JSRuntime: Invoke BitAppShellLocationChangedScroll(url)
    Note over AppShell: AfterRender is triggered
    AppShell->>JSRuntime: Invoke BitAppShellAfterRenderScroll(url)
Loading
sequenceDiagram
    participant TS as AppShell (TypeScript)
    participant Browser as Browser Window
    TS->>TS: Call initScroll(url) to initialize state
    TS->>TS: Invoke locationChangedScroll(url)
    TS->>TS: Remove previous scroll listeners
    TS->>Browser: Set scroll position based on stored value
    TS->>Browser: Add new scroll event listener
Loading

Poem

Hoppin' through the code with a joyful cheer,
A new flag tracks changes, so nothing's unclear.
Scroll behavior now ticks after render's done,
Instant jumps replace smooth moves, oh what fun!
My bunny heart leaps for updates bright as the sun.

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.ts (1)

14-16: Consider adding URL state management.

The locationChangedScroll method only removes the scroll listener but doesn't update the URL state. Consider updating _currentUrl here to maintain consistency.

 public static locationChangedScroll(url: string) {
+    AppShell._currentUrl = url;
     AppShell.removeScroll();
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 32ffa57 and fe750d0.

📒 Files selected for processing (4)
  • src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.razor.cs (2 hunks)
  • src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.ts (2 hunks)
  • src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShellJsRuntimeExtensions.cs (1 hunks)
  • src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Scripts/app.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build and test
🔇 Additional comments (7)
src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShellJsRuntimeExtensions.cs (1)

12-20: LGTM! Clear separation of scroll management responsibilities.

The renaming of BitAppShellNavigateScroll to BitAppShellLocationChangedScroll and the addition of BitAppShellAfterRenderScroll provide a clearer separation of concerns between location change and post-render scroll management.

src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.ts (2)

7-12: LGTM! Improved initialization logic.

The initialization now properly sets up the scroll state for the initial URL.


18-23: LGTM! Robust scroll position restoration.

The afterRenderScroll method properly handles scroll position restoration with fallback to 0 for new URLs and uses 'instant' behavior for a better user experience.

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Scripts/app.ts (1)

7-12: LGTM! Consistent scroll behavior.

The change to 'instant' scroll behavior aligns with the scroll behavior in BitAppShell, providing a consistent user experience across the application.

src/BlazorUI/Bit.BlazorUI.Extras/Components/AppShell/BitAppShell.razor.cs (3)

13-13: LGTM! Added location change tracking.

The _locationChanged flag helps coordinate scroll updates with component rendering.


94-99: LGTM! Proper scroll timing.

The scroll position is now correctly updated after the component has rendered, ensuring that the DOM is in the right state.


107-108: LGTM! Improved location change handling.

The location change handler now properly sets the flag and uses the new scroll method naming.

@msynk msynk merged commit 7735a81 into bitfoundation:develop Feb 17, 2025
3 checks passed
@msynk msynk deleted the 9925-blazorui-appshellp-persistscroll-tuning branch February 17, 2025 19:32
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.

The PersistScroll feature of the BitAppShell component needs some tuning

2 participants