Skip to content

Conversation

@Mydashixiong
Copy link
Collaborator

@Mydashixiong Mydashixiong commented Jun 13, 2025

Link issues

fixes #6219

Summary By Copilot

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

  • Doc is updated/provided or not needed
  • Demo is updated/provided or not needed
  • Merge the latest code from the main branch

Summary by Sourcery

Enable day display in FlipClock by adding a ShowDay parameter and extending the time computation to include days alongside hours, minutes, and seconds.

New Features:

  • Add ShowDay parameter to FlipClock component to toggle day display
  • Extend JavaScript getDate logic to calculate and return days in the timer output

增加ShowDay参数
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jun 13, 2025

Reviewer's Guide

Introduces a ShowDay toggle in the FlipClock component and refactors its JavaScript timer logic to compute a unified days/hours/minutes/seconds breakdown based on elapsed or remaining milliseconds.

Class diagram for FlipClock component

classDiagram
    class FlipClock {
      +bool ShowDay
      +bool ShowHour
    }
Loading

File-Level Changes

Change Details Files
Added ShowDay parameter to conditionally render day digits
  • Define new ShowDay parameter with default false
  • Insert conditional Razor block to render day flip list
src/BootstrapBlazor/Components/FlipClock/FlipClock.razor
src/BootstrapBlazor/Components/FlipClock/FlipClock.razor.cs
Refactored getDate to compute and return days/hours/minutes/seconds
  • Introduce totalMilliseconds variable
  • Compute elapsed or remaining milliseconds for count/countdown modes
  • Clamp negative values in countdown mode
  • Convert totalMilliseconds into days, hours, minutes, seconds
  • Preserve current-date branch returning day/hour/min/sec
src/BootstrapBlazor/Components/FlipClock/FlipClock.razor.js

Possibly linked issues

  • #0: PR adds the ShowDay parameter and related functionality, directly addressing the issue's request to add more parameters.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@bb-auto
Copy link

bb-auto bot commented Jun 13, 2025

Thanks for your PR, @Mydashixiong. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

@bb-auto bb-auto bot requested a review from ArgoZhang June 13, 2025 00:48
@Mydashixiong
Copy link
Collaborator Author

@microsoft-github-policy-service agree

@codecov
Copy link

codecov bot commented Jun 13, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (280219a) to head (19e2fe3).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #6218   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          704       704           
  Lines        31093     31099    +6     
  Branches      4395      4396    +1     
=========================================
+ Hits         31093     31099    +6     
Flag Coverage Δ
BB 100.00% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

sourcery-ai[bot]
sourcery-ai bot previously approved these changes Jun 13, 2025
Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @Mydashixiong - I've reviewed your changes and they look great!

Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments

### Comment 1
<location> `src/BootstrapBlazor/Components/FlipClock/FlipClock.razor.js:22` </location>
<code_context>

     let counter = 0;
     const getDate = () => {
+        let totalMilliseconds = 0;
</code_context>

<issue_to_address>
Consider refactoring the time calculation logic to use a single helper and unified return shape for all branches.

You can collapse the three branches, pull your `counter += 1000` out of each branch, and unify all of the “ms → days/hours/min/sec” logic into a single helper. This both removes duplication and guarantees you always return the same shape (`{days,hours,minutes,seconds}`).

```js
// 1) single helper to break ms into parts
const splitMs = totalMs => {
  const days    = Math.floor(totalMs / 86_400_000);
  const hours   = Math.floor(totalMs / 3_600_000) % 24;
  const minutes = Math.floor(totalMs /   60_000) % 60;
  const seconds = Math.floor(totalMs /    1_000) % 60;
  return { days, hours, minutes, seconds };
};

let counter = 0;
const getDate = () => {
  // 2) increment once if we're in Count or CountDown
  if (options.viewMode === "Count" || options.viewMode === "CountDown") {
    counter += 1000;
  }

  let totalMs;

  switch (options.viewMode) {
    case "Count":
      // elapsed since start
      totalMs = counter - options.startValue;
      break;

    case "CountDown":
      // remaining until zero
      totalMs = Math.max(options.startValue - counter, 0);
      break;

    default:
      // real-time: ms since midnight, days will always be 0
      const now = new Date();
      const midnight = new Date(now).setHours(0, 0, 0, 0);
      totalMs = now - midnight;
  }

  return splitMs(totalMs);
};
```

With this:

- `counter += 1000` lives in one place.  
- You only do “ms → parts” once.  
- You always return `{days,hours,minutes,seconds}` so your rendering logic doesn’t need two shapes.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

const listSecond = el.querySelector('.bb-flip-clock-list.second');
const countDown = options.viewMode === "CountDown";

let counter = 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

issue (complexity): Consider refactoring the time calculation logic to use a single helper and unified return shape for all branches.

You can collapse the three branches, pull your counter += 1000 out of each branch, and unify all of the “ms → days/hours/min/sec” logic into a single helper. This both removes duplication and guarantees you always return the same shape ({days,hours,minutes,seconds}).

// 1) single helper to break ms into parts
const splitMs = totalMs => {
  const days    = Math.floor(totalMs / 86_400_000);
  const hours   = Math.floor(totalMs / 3_600_000) % 24;
  const minutes = Math.floor(totalMs /   60_000) % 60;
  const seconds = Math.floor(totalMs /    1_000) % 60;
  return { days, hours, minutes, seconds };
};

let counter = 0;
const getDate = () => {
  // 2) increment once if we're in Count or CountDown
  if (options.viewMode === "Count" || options.viewMode === "CountDown") {
    counter += 1000;
  }

  let totalMs;

  switch (options.viewMode) {
    case "Count":
      // elapsed since start
      totalMs = counter - options.startValue;
      break;

    case "CountDown":
      // remaining until zero
      totalMs = Math.max(options.startValue - counter, 0);
      break;

    default:
      // real-time: ms since midnight, days will always be 0
      const now = new Date();
      const midnight = new Date(now).setHours(0, 0, 0, 0);
      totalMs = now - midnight;
  }

  return splitMs(totalMs);
};

With this:

  • counter += 1000 lives in one place.
  • You only do “ms → parts” once.
  • You always return {days,hours,minutes,seconds} so your rendering logic doesn’t need two shapes.

@ArgoZhang ArgoZhang changed the title 修改FlipClock feat(FlipClock): add ShowDay parameter Jun 13, 2025
@bb-auto bb-auto bot added the enhancement New feature or request label Jun 13, 2025
@bb-auto bb-auto bot added this to the 9.7.0 milestone Jun 13, 2025
ArgoZhang
ArgoZhang previously approved these changes Jun 13, 2025
@ArgoZhang ArgoZhang enabled auto-merge (squash) June 13, 2025 02:56
@dotnet-policy-service
Copy link

@Mydashixiong please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@dotnet-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@dotnet-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@dotnet-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ),
and conveys certain license rights to the .NET Foundation ( “.NET Foundation” ) for Your contributions to
.NET Foundation open source projects. This Agreement is effective as of the latest signature date below.

1. Definitions.

“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to .NET Foundation under this Agreement.

“Project” means any of the projects owned or managed by .NET Foundation and offered under a license
approved by the Open Source Initiative (www.opensource.org).

“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”

“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.

2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.

3. Originality of Work. You represent that each of Your Submissions is entirely Your
original work. Should You wish to Submit materials that are not Your original work,
You may Submit them separately to the Project if You (a) retain all copyright and
license information that was in the materials as you received them, (b) in the
description accompanying your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any
licenses or other restrictions of which You are aware, and (c) follow any other
instructions in the Project's written guidelines concerning Submissions.

4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.

5. Licenses.

a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly
or indirectly from .NET Foundation, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable
license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform,
and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing
rights to third parties.

b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or
indirectly from .NET Foundation, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license
under Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.

c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3 ). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6 , THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or
circumstances of which You later become aware that would make Your representations in this
Agreement inaccurate in any respect.

8. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.

9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.

10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by .NET Foundation.

.NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1.

@Mydashixiong
Copy link
Collaborator Author

@dotnet-policy-service agree

@ArgoZhang ArgoZhang disabled auto-merge June 13, 2025 03:22
@ArgoZhang ArgoZhang merged commit 1c0abc4 into main Jun 13, 2025
4 of 6 checks passed
@ArgoZhang ArgoZhang deleted the FlipClock branch June 13, 2025 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(FlipClock): add ShowDay parameter

3 participants