-
Notifications
You must be signed in to change notification settings - Fork 82
936558: Resolved the conflict for Angular docs #779
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
base: master
Are you sure you want to change the base?
Conversation
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INQUEUE 🕒 |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Build Status: INPROGRESS 🔃 |
CI Status: FAILURE ❌ |
Feature description
Need to Resolve conflict files
Requirement and specification document.
Need to Resolve conflict files
API Review task
NA
Output screenshots
NA
Feature matrix document
Feature matrix document updated against this feature and committed in this common location](https://syncfusion.sharepoint.com/sites/EJ2ProductOwners/Shared%20Documents/Forms/AllItems.aspx?viewid=ae81c682%2D3d0f%2D462a%2Db8ec%2D7358748d489d&id=%2Fsites%2FEJ2ProductOwners%2FShared%20Documents%2FGeneral%2FFeature%20Matrix%20%2D%20Documents)&xsdata=MDV8MDJ8fDYxYWU4YmIxYWVlOTQxZjRjZTUxMDhkZDQwMzMzYWE5fDc3ZjFmZTEyYjA0OTQ5MTk4YzUwOWZiNDFlNWJiNjNifDB8MHw2Mzg3MzczMTA5MjgxOTUxNTN8VW5rbm93bnxWR1ZoYlhOVFpXTjFjbWwwZVZObGNuWnBZMlY4ZXlKV0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpvaVYybHVNeklpTENKQlRpSTZJazkwYUdWeUlpd2lWMVFpT2pFeGZRPT18MXxMMk5vWVhSekx6RTVPak0yWm1abFpqQTVMVGcxWm1NdE5ERTFaQzA1T1RVeUxUYzVNVGN6T0dFeE5qTTFORjlsWWpSaFlqazBZUzB5WlRJd0xUUTNZVFl0WW1VeU1TMWxOMk0xTW1Oa1lqRTFabVJBZFc1eExtZGliQzV6Y0dGalpYTXZiV1Z6YzJGblpYTXZNVGN6T0RFek5ESTVNakF3TXc9PXw1OWU2ZjU2ZTg2ODk0YTc4Y2U1MTA4ZGQ0MDMzM2FhOXwxODM0NGYxZTgzMWY0YWY2YTE4YWMxY2IwMzU3Zjk3ZA%3D%3D&sdata=RFc3djhRZGRINDdUMGg3SUorSnJ6dy9FM0NFYzlLalk3cnR2eCtsRjN6az0%3D&ovuser=77f1fe12-b049-4919-8c50-9fb41e5bb63b%2Celayabharathi.n%40syncfusion.com) .
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