Skip to content

927787: Resolve conflicts in Angular UG documentation page #700

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

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

JosephHerson
Copy link
Contributor

Feature description

Resolve conflicts in Angular UG documentation page

Requirement and specification document.

Resolve conflicts in Angular UG documentation page

API Review task

NA

Output screenshots

NA

Feature matrix document

Feature matrix document updated against this feature and committed in this common location .

  • Yes
  • NO
  • NA

Provide the details about the areas or combinations which have been tested against this code changes.

  • Tested against feature matrix.

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.

  • BUnit, share corresponding MR.
  • E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.

Test bed sample location

NA

Feature completion checklist

UX changes got approval if UI is added or modified?

  • Yes
  • NO
  • NA

Drafted UG for this feature?

  • Yes
  • NO
  • NA

Content team reviewed the UI content changes.

  • Yes
  • NO
  • NA

Is this the common feature which needs to be addressed in the same component or on other components in our platform?

  • Yes
  • NO

Is there any existing behavior change due to this code change?

  • Yes
  • NO

Blazor Checklist

Confirm whether the ensured feature is in both Blazor Server and WASM.

  • Yes
  • NO
  • NA

Do the code changes cause any memory leak and performance issue?

  • Yes
  • NO

Reviewer Checklist

  • All provided information are reviewed and ensured.

@SyncfusionBuild
Copy link
Contributor

CI Status: FAILURE ❌
Source Compilation: Not Started ❌
Build Location: conflict

@Mydeensn Mydeensn merged commit 6ab2b2f into master Dec 12, 2024
1 check failed
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.

3 participants