Skip to content

Conversation

@ArgoZhang
Copy link
Member

@ArgoZhang ArgoZhang commented Jan 1, 2026

Link issues

fixes #884

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

Update holiday component data files to include holidays for the year 2026.

New Features:

  • Add 2026 holiday data JSON for the Holiday component.

Enhancements:

  • Adjust Holiday component project configuration to reference the new 2026 holiday data file.

Copilot AI review requested due to automatic review settings January 1, 2026 07:56
@bb-auto bb-auto bot added the enhancement New feature or request label Jan 1, 2026
@bb-auto bb-auto bot added this to the v9.2.0 milestone Jan 1, 2026
@sourcery-ai
Copy link

sourcery-ai bot commented Jan 1, 2026

🧙 Sourcery has finished reviewing your pull request!


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

@ArgoZhang ArgoZhang merged commit 1226b9e into master Jan 1, 2026
5 of 6 checks passed
@ArgoZhang ArgoZhang deleted the feat-holiday branch January 1, 2026 07:57
Copy link

@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 - I've left some high level feedback:

  • Please double-check that the new 2026.json is wired into the .csproj in the same way as the existing holiday data files (e.g., build action, copy settings, and item group structure) to avoid inconsistent behavior at runtime.
  • Ensure the structure and key names in Data/2026.json match the previous years’ JSON files so that the Holiday component can parse the new data without additional code changes.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Please double-check that the new `2026.json` is wired into the `.csproj` in the same way as the existing holiday data files (e.g., build action, copy settings, and item group structure) to avoid inconsistent behavior at runtime.
- Ensure the structure and key names in `Data/2026.json` match the previous years’ JSON files so that the Holiday component can parse the new data without additional code changes.

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.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds Chinese holiday data for the year 2026 to the BootstrapBlazor.Holiday component and bumps the package version to 10.0.1. The new data file follows the established JSON structure used for previous years (2016-2025) and includes major Chinese holidays with their respective dates, holiday periods, and make-up working days.

  • Adds 2026.json with holiday and working day definitions for all major Chinese holidays
  • Increments package version from implicit to explicit 10.0.1

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
src/components/BootstrapBlazor.Holiday/Data/2026.json New holiday data file for 2026 containing Chinese holiday schedules including Spring Festival, Qingming, Labor Day, Dragon Boat Festival, Mid-Autumn Festival, and National Day with their associated make-up working days
src/components/BootstrapBlazor.Holiday/BootstrapBlazor.Holiday.csproj Adds explicit version property set to 10.0.1, appropriate for a minor content update

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +4 to +64
"range": [ "2026-01-01", "2026-01-03" ],
"type": "holiday"
},
{
"name": "元旦",
"range": [ "2026-01-04" ],
"type": "workingday"
},
{
"name": "春节",
"range": [ "2026-02-14" ],
"type": "workingday"
},
{
"name": "春节",
"range": [ "2026-02-15", "2026-02-23" ],
"type": "holiday"
},
{
"name": "春节",
"range": [ "2026-02-28" ],
"type": "workingday"
},
{
"name": "清明节",
"range": [ "2026-04-04", "2026-04-06" ],
"type": "holiday"
},
{
"name": "劳动节",
"range": [ "2026-05-01", "2026-05-05" ],
"type": "holiday"
},
{
"name": "劳动节",
"range": [ "2026-05-09" ],
"type": "workingday"
},
{
"name": "端午节",
"range": [ "2026-06-19", "2026-06-21" ],
"type": "holiday"
},
{
"name": "中秋节",
"range": [ "2026-09-20" ],
"type": "workingday"
},
{
"name": "中秋节",
"range": [ "2026-09-25", "2026-09-27" ],
"type": "holiday"
},
{
"name": "国庆节",
"range": [ "2026-10-01", "2026-10-07" ],
"type": "holiday"
},
{
"name": "国庆节",
"range": [ "2026-10-10" ],
Copy link

Copilot AI Jan 1, 2026

Choose a reason for hiding this comment

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

The array formatting in the "range" fields is inconsistent with the existing data files. All other year files (2016-2025) use compact array notation without spaces, e.g., ["2025-01-01", "2025-01-03"], but this file uses spaces inside the brackets, e.g., [ "2026-01-01", "2026-01-03" ].

For consistency with the established codebase convention, remove the spaces after the opening bracket and before the closing bracket in all "range" arrays throughout this file.

Suggested change
"range": [ "2026-01-01", "2026-01-03" ],
"type": "holiday"
},
{
"name": "元旦",
"range": [ "2026-01-04" ],
"type": "workingday"
},
{
"name": "春节",
"range": [ "2026-02-14" ],
"type": "workingday"
},
{
"name": "春节",
"range": [ "2026-02-15", "2026-02-23" ],
"type": "holiday"
},
{
"name": "春节",
"range": [ "2026-02-28" ],
"type": "workingday"
},
{
"name": "清明节",
"range": [ "2026-04-04", "2026-04-06" ],
"type": "holiday"
},
{
"name": "劳动节",
"range": [ "2026-05-01", "2026-05-05" ],
"type": "holiday"
},
{
"name": "劳动节",
"range": [ "2026-05-09" ],
"type": "workingday"
},
{
"name": "端午节",
"range": [ "2026-06-19", "2026-06-21" ],
"type": "holiday"
},
{
"name": "中秋节",
"range": [ "2026-09-20" ],
"type": "workingday"
},
{
"name": "中秋节",
"range": [ "2026-09-25", "2026-09-27" ],
"type": "holiday"
},
{
"name": "国庆节",
"range": [ "2026-10-01", "2026-10-07" ],
"type": "holiday"
},
{
"name": "国庆节",
"range": [ "2026-10-10" ],
"range": ["2026-01-01", "2026-01-03"],
"type": "holiday"
},
{
"name": "元旦",
"range": ["2026-01-04"],
"type": "workingday"
},
{
"name": "春节",
"range": ["2026-02-14"],
"type": "workingday"
},
{
"name": "春节",
"range": ["2026-02-15", "2026-02-23"],
"type": "holiday"
},
{
"name": "春节",
"range": ["2026-02-28"],
"type": "workingday"
},
{
"name": "清明节",
"range": ["2026-04-04", "2026-04-06"],
"type": "holiday"
},
{
"name": "劳动节",
"range": ["2026-05-01", "2026-05-05"],
"type": "holiday"
},
{
"name": "劳动节",
"range": ["2026-05-09"],
"type": "workingday"
},
{
"name": "端午节",
"range": ["2026-06-19", "2026-06-21"],
"type": "holiday"
},
{
"name": "中秋节",
"range": ["2026-09-20"],
"type": "workingday"
},
{
"name": "中秋节",
"range": ["2026-09-25", "2026-09-27"],
"type": "holiday"
},
{
"name": "国庆节",
"range": ["2026-10-01", "2026-10-07"],
"type": "holiday"
},
{
"name": "国庆节",
"range": ["2026-10-10"],

Copilot uses AI. Check for mistakes.
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(Holiday): update holiday data for 2026

2 participants