Skip to content

Conversation

@msynk
Copy link
Member

@msynk msynk commented Jun 5, 2025

closes #10922

Summary by CodeRabbit

  • Bug Fixes
    • Improved the update process to handle updates more reliably and ensure smoother application reloads when updates are available.

@msynk msynk requested a review from ysmoradi June 5, 2025 04:47
@coderabbitai
Copy link

coderabbitai bot commented Jun 5, 2025

Walkthrough

The forceUpdate method in the App class was refactored to be asynchronous. It now utilizes the skipWaiting API from Bswup, conditionally exits early based on its result, and configures BitBswupProgress before checking for updates. The method signature was updated to reflect its asynchronous nature.

Changes

File(s) Change Summary
src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Scripts/app.ts Refactored forceUpdate to async, integrated skipWaiting API, added early exit, updated method signature

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant window.BitBswup
    participant window.BitBswupProgress

    User->>App: Call forceUpdate()
    App->>window.BitBswup: skipWaiting()
    alt skipWaiting returns truthy
        App-->>User: Return (early exit)
    else skipWaiting returns falsy
        App->>window.BitBswupProgress: configure({ autoReload: true })
        App->>window.BitBswup: checkForUpdate()
        App-->>User: Return
    end
Loading

Assessment against linked issues

Objective Addressed Explanation
Use the new skipWaiting API of the Bswup in the force-update method (Issue #10922)

Poem

A hop and a skip, the update is here,
With async delight, the code’s crystal clear.
Now Bswup will wait, or swiftly proceed,
The rabbit approves—this change is a deed!
So onward we bound, with updates in tow,
The boilerplate’s ready—let progress now flow! 🐇✨

✨ 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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

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: 2

🧹 Nitpick comments (1)
src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Scripts/app.ts (1)

84-85: The update logic is correct, but consider adding error handling.

The sequence of configuring the progress handler before checking for updates is logical and correct.

Consider wrapping these operations in error handling for robustness:

-    bswupProgress.config({ autoReload: true });
-    bswup.checkForUpdate();
+    try {
+        bswupProgress.config({ autoReload: true });
+        bswup.checkForUpdate();
+    } catch (error) {
+        console.error('Failed to configure or check for updates:', error);
+    }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 52c41ec and 6c145c3.

📒 Files selected for processing (1)
  • src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Scripts/app.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build and test
🔇 Additional comments (1)
src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Core/Scripts/app.ts (1)

78-78:

❓ Verification inconclusive

Verify that all callers handle the async method signature change.

The method signature change from synchronous to asynchronous is a breaking change. Ensure that all existing callers of forceUpdate() have been updated to properly await the call or handle the returned Promise.


🏁 Script executed:

#!/bin/bash
# Description: Find all callers of forceUpdate method to verify they handle the async nature
# Expected: All callers should either await the call or handle the Promise

echo "Searching for calls to App.forceUpdate()..."
rg -A 3 -B 1 "\.forceUpdate\(\)" --type ts --type js --type tsx --type jsx

echo "Searching for calls to forceUpdate()..."
rg -A 3 -B 1 "forceUpdate\(\)" --type ts --type js --type tsx --type jsx

Length of output: 393


Verify Async Breaking Change for App.forceUpdate

The forceUpdate method was changed from synchronous:

public static forceUpdate() {  }

to asynchronous:

public static async forceUpdate() {  }

This is a breaking change to the public API. Ensure that every invocation has been updated to handle the returned Promise (e.g. using await or .then).

• Run this search to locate all call sites:

grep -RIn --include=\*.{ts,tsx,js,jsx} -C2 "forceUpdate(" .

• Verify in each file that calls to App.forceUpdate() or forceUpdate() are properly awaited or chained.
• Update any missing await/.then to avoid unhandled Promise issues.

@msynk msynk merged commit 9b0c89c into bitfoundation:develop Jun 5, 2025
3 checks passed
@msynk msynk deleted the 10922-templates-boilerplate-bswup-skipwaiting branch June 5, 2025 05:59
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 Boilerplate project template needs to use the new skipWaiting api of the Bswup in its force-update

1 participant