@syncfusion/ej2-treegrid 24.2.7 → 24.2.8

package/dist/global/index.d.ts

@@ -1,6 +1,6 @@
 /*!
 *  filename: index.d.ts
-*  version : 24.2.7
+*  version : 24.2.8
 *  Copyright Syncfusion Inc. 2001 - 2023. All rights reserved.
 *  Use of this code is subject to the terms of our license.
 *  A copy of the current license can be obtained at any time by e-mailing

package/package.json

@@ -1,8 +1,8 @@
 {
   "_from": "@syncfusion/ej2-treegrid@*",
-  "_id": "@syncfusion/ej2-treegrid@24.2.5",
+  "_id": "@syncfusion/ej2-treegrid@24.2.7",
   "_inBundle": false,
-  "_integrity": "sha512-/ddOZwHICi92QoxX5p1kwqFtc4cIVL8JJgo5IR11sNJ+SsPcde2ao/eIGTPgii6SpdV24cWcj3vZHXFqUKk9Fg==",
+  "_integrity": "sha512-OoM88SgilK7jJcbH2DdoMzGAOTDf7kPBtDxaVHjwD8vovfoVkUeTNwipnQKLRLDUbAfFcz2JOPnc34uph98UWw==",
   "_location": "/@syncfusion/ej2-treegrid",
   "_phantomChildren": {},
   "_requested": {
@@ -24,8 +24,8 @@
     "/@syncfusion/ej2-react-treegrid",
     "/@syncfusion/ej2-vue-treegrid"
   ],
-  "_resolved": "https://nexus.syncfusioninternal.com/repository/ej2-hotfix-new/@syncfusion/ej2-treegrid/-/ej2-treegrid-24.2.5.tgz",
-  "_shasum": "00dfe46c48c665b1e18b46a0193867238dd9dcae",
+  "_resolved": "https://nexus.syncfusioninternal.com/repository/ej2-hotfix-new/@syncfusion/ej2-treegrid/-/ej2-treegrid-24.2.7.tgz",
+  "_shasum": "4c8aeece891894c115b1bb14a24cf6907a12b4fa",
   "_spec": "@syncfusion/ej2-treegrid@*",
   "_where": "/jenkins/workspace/elease-automation_release_24.1.1/packages/included",
   "author": {
@@ -38,8 +38,8 @@
   "dependencies": {
     "@syncfusion/ej2-base": "~24.2.7",
     "@syncfusion/ej2-data": "~24.2.3",
-    "@syncfusion/ej2-grids": "~24.2.7",
-    "@syncfusion/ej2-popups": "~24.2.5"
+    "@syncfusion/ej2-grids": "~24.2.8",
+    "@syncfusion/ej2-popups": "~24.2.8"
   },
   "deprecated": false,
   "description": "Essential JS 2 TreeGrid Component",
@@ -66,6 +66,6 @@
     "url": "git+https://github.com/syncfusion/ej2-treegrid.git"
   },
   "typings": "index.d.ts",
-  "version": "24.2.7",
+  "version": "24.2.8",
   "sideEffects": false
 }

package/src/treegrid/actions/edit.js

@@ -92,6 +92,7 @@ var Edit = /** @class */ (function () {
     };
     Edit.prototype.beforeBatchCancel = function (args) {
         if (this.parent.editSettings.mode === 'Cell') {
+            args['requestType'] = 'cancel';
             this.parent.trigger(events.actionComplete, args);
         }
     };

package/src/treegrid/base/treegrid.js

@@ -2849,6 +2849,9 @@ var TreeGrid = /** @class */ (function (_super) {
                         record = this.grid.getCurrentViewRecords()[row.rowIndex];
                     }
                 }
+                else if (this.rowTemplate) {
+                    record = this.grid.getCurrentViewRecords()[row.rowIndex];
+                }
                 else {
                     record = this.grid.getCurrentViewRecords()[parseInt(row.getAttribute('data-rowindex'), 10)];
                 }

package/.github/PULL_REQUEST_TEMPLATE/Bug.md

@@ -1,60 +0,0 @@
-### Bug description
-
-Clearly and concisely describe the problem or feature (this cannot be empty).
-
-### Root cause
-
-Briefly describe the root cause and analysis of the problem.
-If there is an internal discussion on the forum, provide the link.
-### Reason for not identifying earlier
-
-Find how it was missed in our earlier testing and development by analysing the below checklist. This will help prevent similar mistakes in the future. 
-
- - [ ] Guidelines/documents are not followed
-
-    - Common guidelines / Core team guideline
-    - Specification document
-    - Requirement document
-
- - [ ] Guidelines/documents are not given
-
-
-    - Common guidelines / Core team guideline
-    - Specification document
-    - Requirement document
-
-
-### Reason:
-Mention any one or more reasons from the above points.
-
-### Action taken:
-What action did you take to avoid this in future?
-
-### Related areas:
-Is there any other related areas also to be addressed?
-
-
-### Is it a breaking issue?
-
-If it is a breaking issue, provide the commit detail which caused this break.
-
-### Solution description
-
-Describe your code changes in detail for reviewers.
-
-### Output screenshots
-
-Post the output screenshots if an UI is affected or added due to this bug.
-### Areas affected and ensured
-
-List the areas affected by your code changes.
-
-### Additional checklist
-This may vary for different teams or products. Check with your scrum masters.
-
-  - Did you run the automation against your fix?
-  - Is there any API name change?
-  - Is there any existing behavior change of other features due to this code change?
-  - Does your new code introduce new warnings or binding errors?
-  - Does your code pass all FxCop and StyleCop rules?
-  - Did you record this case in the unit test or UI test?

package/.github/PULL_REQUEST_TEMPLATE/feature.md

@@ -1,37 +0,0 @@
-### Feature description
-
-Clearly and concisely describe the problem or feature (this cannot be empty).
-
-### Analysis and design
-
-If there is an external design, link to its project documentation area.
-If there is an internal discussion on the forum, provide the link.
-### Solution description
-
-Describe your code changes in detail for reviewers.
-
-### Output screenshots
-
-Post the output screenshots if an UI is affected or added due to this feature.
-### Areas affected and ensured
-
-List the areas are affected by your code changes.
-
-### 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.
-Test bed 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.
-
-### Additional checklist
-This may vary for different teams or products. Check with your scrum masters.
-
-  - Did you run the automation against your fix?
-  - Is there any API name change?
-  - Is there any existing behavior change of other features due to this code change?
-  - Does your new code introduce new warnings or binding errors?
-  - Does your code pass all FxCop and StyleCop rules?
-  - Did you record this case in the unit test or UI test?