Skip to content

961466: Include UG for set work days #6289

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: development
Choose a base branch
from

Conversation

VijayakumarRSF4470
Copy link
Contributor

@VijayakumarRSF4470 VijayakumarRSF4470 commented Jul 10, 2025

Feature description

961466 - Include the UG for SetWorkDaysAsync and ResetWorkDaysAsync methods.

Analysis and design

We analyzed how to demonstrate the use case of SetWorkDays in our documentation, and then decided to showcase the functionality by displaying working days for individual resources while excluding both common organization-wide holidays and resource-specific leaves

Solution description

We analyzed how to demonstrate the use case of SetWorkDays in our documentation, and then decided to showcase the functionality by displaying working days for individual resources while excluding both common organization-wide holidays and resource-specific leaves

Output screenshots

blazor-scheduler-setWorkDays-resetWorkDays

Areas affected and ensured

NA

API Changes

NA

Added:

  • string ListView.GroupName { get; set; } //Bindable Property
  • int ListView.GroupId { get; set; } // Bindable Property
  • void ListView.Clear ();

Changed:

  • object ListView.SelectedItem => Cell ListView.SelectedItem

Behavioral Changes

NA

Test cases

Provide the unit testing written file details to understand the use cases considered in this implementation.
If there is no TDD (if it’s not possible to follow), provide the UI automation script location and the Excel file that contains the use cases considered in this implementation.
Provide the test cases Excel file alone if the feature cannot be automated in any case.

List out all the scenarios you have tested after include these changes. You can refer the predefined scenarios from below link.

https://syncfusion.atlassian.net/wiki/display/CHARTXAMARIN/Chart+Test+Plan

Testbed sample location

Provide the test bed sample location where code reviewers can review the new feature’s behaviors. This depends on the CI process that your team follows. It can be from NPMCI, HockeyApp, staging site, local server, etc.

Does it have any known issues?

NA

Does it have memory leak?

NA

MR CheckList

  • Does it follow the design guidelines? It is mandatory that, we should not move the changes without reading this.
  • Did UI automation passed without errors? If it is customer issue, make sure it is included in the IR automation.
  • Properly working in Xamarin.Forms previewer.
  • Ensured in iOS, Android, UWP and macOS (if supported).
  • Have you added API comments if it is new API?
  • Does it need localization? If so, update resx file in GitHub.
  • Whether we have added new APIs? If so, whether it is as per the guidelines?
  • If changes are made in the Xamarin.Forms sample browser project file, whether it is included in the props file too? If not, your sample level changes will not reflect in the application published in the hockey app.
  • Have you ensured the changes in Android API 19 and iOS 9?

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

Build Status: INQUEUE 🕒
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

Build Status: INQUEUE 🕒
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: FAILURE ❌
Source Compilation: SUCCESS ✅
Failure Reason: CI Failure with violation
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 5
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

@SyncfusionBuild
Copy link
Contributor

The running CI Job is terminated due to changes committed on the source branch for this Merge Request and CI triggered for latest commit.

@SyncfusionBuild
Copy link
Contributor

CI Status: ABORTED ❌
Source Compilation: Not Started ❌
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: ES-961466-SetWorkDoc

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: ES-961466-SetWorkDoc
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants