908922: Resolve merge conflict #644
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing node entry in the TOC.html file
|
Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly. |
|
Your pull request has been created. Syncfusion support team will validate this commit and publish your changes accordingly. |
DeepakRajSundar
approved these changes
Jun 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature description
Need to resolve merge conflict
Requirement and specification document.
966204
API Review task
NA
Output screenshots
NA
Feature matrix document
Feature matrix document updated against this feature and committed in this common location .
Provide the details about the areas or combinations which have been tested against this code changes.
Feature acceptance criteria (Test-case document)
Draft the test cases in excel and attach it in the MR itself. The automation must be covered based on this positive and worst-case test-cases.
Automation details
Mark 'Is Automated' field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the feature is automated.
Test bed sample location
Provide the test bed sample location where the code reviewers can review the new feature’s behaviors.
Feature completion checklist
UX changes got approval if UI is added or modified?
Drafted UG for this feature?
Content team reviewed the UI content changes.
Is this the common feature which needs to be addressed in the same component or on other components in our platform?
Is there any existing behavior change due to this code change?
Blazor Checklist
Confirm whether the ensured feature is in both Blazor Server and WASM.
Do the code changes cause any memory leak and performance issue?
Reviewer Checklist