Use RenderInfo.IsInteractive instead of internal reflection in Boilerplate (#10250)

[ysmoradi]

closes #10250

Summary by CodeRabbit

• Refactor
  • Updated the logic for detecting the rendering mode during initialization, ensuring a more accurate switch between static and interactive states. This change may lead to more consistent component behavior during pre-rendering sessions.

[coderabbitai]

Walkthrough

The changes update the logic used to determine if a component is running in a prerender session. Both the AppComponentBase and the MainLayout now check the interactivity of the renderer via RendererInfo.IsInteractive instead of relying on the initialization state of the JavaScript runtime. This adjustment modifies the conditions under which the application decides it is in a prerender mode, thereby potentially affecting component behavior during initialization.

Changes

Files	Change Summary
src/Templates/Boilerplate/Bit.Boilerplate/.../Components/AppComponentBase.cs src/Templates/Boilerplate/Bit.Boilerplate/.../Components/Layout/MainLayout.razor.cs	Replaced the JavaScript runtime initialization check with a check on RendererInfo.IsInteractive to determine prerender session status. In AppComponentBase.cs, the InPrerenderSession property logic was updated. In MainLayout.razor.cs, the variable inPrerenderSession in OnInitializedAsync now uses the new renderer interactivity condition, potentially affecting the isOnline status.

Sequence Diagram(s)

sequenceDiagram
    participant C as Component
    participant R as RendererInfo
    participant Env as Runtime Environment

    C->>R: Check if IsInteractive?
    alt Renderer is not interactive
        C->>Env: Treat as prerender session
    else Renderer is interactive
        C->>Env: Continue normal initialization
    end

Loading

Poem

Oh, I’m just a rabbit with a joyful hop,
Skipping through code where old checks drop.
Renderer now leads the parade with flair,
Pre-render mode’s clearer, light as air.
Hopping in the code field, I cheer with glee –
A smarter start for you and me!
🐇💻 Happy coding, let your logic be free!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bc33f38 and 4fe588a.

📒 Files selected for processing (2)

• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/AppComponentBase.cs (1 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Layout/MainLayout.razor.cs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build and test

🔇 Additional comments (2)

src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/AppComponentBase.cs (1)

68-68: Improved prerender detection using official API

The change replaces internal reflection with the official RendererInfo.IsInteractive property to determine if a component is in a prerender session. This is a more maintainable approach that relies on the public API rather than implementation details.

src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Components/Layout/MainLayout.razor.cs (1)

44-44: Consistent prerender detection approach

This change aligns with the update in AppComponentBase.cs, using RendererInfo.IsInteractive instead of checking the JavaScript runtime initialization. This creates consistency across the codebase and uses the correct official API for detecting prerender state.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
• @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.