Skip to content

965810: Added a block editor UG in main repo #646

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 2 commits into from
Jun 25, 2025

Conversation

premanandh2205
Copy link
Contributor

Feature description

Need to port the content for the Block editor component in the main repo

Requirement and specification document.

NA

API Review task

NA

Output screenshots

NA

Feature matrix document

  • 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)

NA

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. Provide Task link.
  • NO
  • NA

Drafted UG for this feature?

  • Yes, provide MR link.
  • NO, provide task link.
  • NA

Content team reviewed the UI content changes.

  • Yes. Provide MR or Task link.
  • NO
  • NA

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

  • Yes. If we need to check in other components, tag "needs-attention-coreteam"
  • NO

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

  • Yes. If So, add breaking-change label.
  • 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

  • Reviewed feature matrix document modifications and reviewed developer testing report against the feature matrix reviewed.
  • Testbed sample ensured.
  • Coverage report checked.
  • Ensured the code changes meet the coding standard.
  • Confirming script changes made in this merge request can't be achieved in C#.

Created task in Blazor to synchronize if the feature is not available and applicable.

  • NA
  • Yes, task link.
  • NO, share reason.

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: 965810-BE-master

@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: 965810-BE-master

@SyncfusionBuild
Copy link
Contributor

Build Status: INPROGRESS 🔃
Build Location: 965810-BE-master

@SyncfusionBuild
Copy link
Contributor

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: 965810-BE-master

@kalirajanganeshan kalirajanganeshan merged commit afe0c61 into master Jun 25, 2025
1 check passed
@IndrajithSrinivasan IndrajithSrinivasan deleted the 965810-BE-master branch June 25, 2025 09:48
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.

5 participants