@syncfusion/ej2-vue-base 24.2.3 → 25.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,11 +2,13 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## 25.1.35 (2024-03-15)
6
+
5
7
  ### Common
6
8
 
7
9
  #### Bug Fixes
8
10
 
9
- - `#I528934` - The issue with "Reactivity is not working in Vue Grid component" has been resolved.
11
+ - `#I552563` - The issue with "the TypeScript intellisense is not shown in the Vue components" has been resolved.
10
12
 
11
13
  ## 24.1.41 (2023-12-18)
12
14
 
@@ -1,6 +1,6 @@
1
1
  /*!
2
2
  * filename: ej2-vue-base.umd.min.js
3
- * version : 24.2.3
3
+ * version : 25.2.3
4
4
  * Copyright Syncfusion Inc. 2001 - 2023. All rights reserved.
5
5
  * Use of this code is subject to the terms of our license.
6
6
  * A copy of the current license can be obtained at any time by e-mailing
@@ -1,6 +1,6 @@
1
1
  /*!
2
2
  * filename: ej2-vue-base.min.js
3
- * version : 24.2.3
3
+ * version : 25.2.3
4
4
  * Copyright Syncfusion Inc. 2001 - 2023. All rights reserved.
5
5
  * Use of this code is subject to the terms of our license.
6
6
  * A copy of the current license can be obtained at any time by e-mailing
@@ -1,6 +1,6 @@
1
1
  /*!
2
2
  * filename: index.d.ts
3
- * version : 24.2.3
3
+ * version : 25.2.3
4
4
  * Copyright Syncfusion Inc. 2001 - 2023. All rights reserved.
5
5
  * Use of this code is subject to the terms of our license.
6
6
  * A copy of the current license can be obtained at any time by e-mailing
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "_from": "@syncfusion/ej2-vue-base@*",
3
- "_id": "@syncfusion/ej2-vue-base@24.1.41",
3
+ "_id": "@syncfusion/ej2-vue-base@25.1.35",
4
4
  "_inBundle": false,
5
- "_integrity": "sha512-/2amQIoKRilTvcJt2rTPRKY3YpVrbSdEnSHDWyyy7WzQ936xjZziUjM/28+Q2+IHtIS0KN98HkrgbiAv3lHINg==",
5
+ "_integrity": "sha512-gLdS0YWsQDruh6imDgDLGnricHT032zcz/SL9qok14ts4DNdkDDGZCMlDdx4flpUtt5Pay8JrPlOo7ncMwk10Q==",
6
6
  "_location": "/@syncfusion/ej2-vue-base",
7
7
  "_phantomChildren": {},
8
8
  "_requested": {
@@ -53,10 +53,10 @@
53
53
  "/@syncfusion/ej2-vue-treegrid",
54
54
  "/@syncfusion/ej2-vue-treemap"
55
55
  ],
56
- "_resolved": "https://nexus.syncfusion.com/repository/ej2-hotfix-new/@syncfusion/ej2-vue-base/-/ej2-vue-base-24.1.41.tgz",
57
- "_shasum": "6c5cbfe26bb9a916b53c87649c6f8c1a47ca49c9",
56
+ "_resolved": "https://nexus.syncfusioninternal.com/repository/ej2-hotfix-new/@syncfusion/ej2-vue-base/-/ej2-vue-base-25.1.35.tgz",
57
+ "_shasum": "08afaaf856ce3947e9e7030326e74072917dc49c",
58
58
  "_spec": "@syncfusion/ej2-vue-base@*",
59
- "_where": "/jenkins/workspace/elease-automation_release_24.1.1/packages/included",
59
+ "_where": "/jenkins/workspace/elease-automation_release_25.1.1/packages/included",
60
60
  "author": {
61
61
  "name": "Syncfusion Inc."
62
62
  },
@@ -65,7 +65,7 @@
65
65
  },
66
66
  "bundleDependencies": false,
67
67
  "dependencies": {
68
- "@syncfusion/ej2-base": "~24.2.3"
68
+ "@syncfusion/ej2-base": "~25.2.3"
69
69
  },
70
70
  "deprecated": false,
71
71
  "description": "A common package of Essential JS 2 base Vue libraries, methods and class definitions",
@@ -95,6 +95,6 @@
95
95
  "compile": "gulp ci-compile"
96
96
  },
97
97
  "typings": "index.d.ts",
98
- "version": "24.2.3",
98
+ "version": "25.2.3",
99
99
  "sideEffects": true
100
100
  }
@@ -1,4 +1,22 @@
1
1
  export declare const isExecute: boolean, aVue: any, gh: any;
2
2
  export declare let vueDefineComponent: (options: any) => any;
3
- export declare let ComponentBase: any;
3
+ declare type ComponentBase = {
4
+ getInjectedServices(): Object[];
5
+ updated(): void;
6
+ bindProperties(): void;
7
+ assignValueToWrapper(option: Object, silent?: boolean): void;
8
+ fetchChildPropValues(childOption: Object): void;
9
+ getDirectiveValues(tagDirectives: any, tagMapper: {
10
+ [key: string]: Object;
11
+ }, tagNameMapper: Object): Object;
12
+ getMultiLevelDirValue(tagDirectories: any, tagKey: string | Object, tagNameMapper: Object): Object;
13
+ getVNodeValue(tagDirective: any, tagKey: string | Object, tagNameMapper: Object): Object;
14
+ /**
15
+ * convert kebab case directive props to camel case
16
+ */
17
+ getCamelCaseProps(props: Object): Object;
18
+ dataBind(): void;
19
+ };
20
+ export declare let ComponentBase: ComponentBase;
4
21
  export declare function getProps(options?: any): any;
22
+ export {};
@@ -1,60 +0,0 @@
1
- ### Bug description
2
-
3
- Clearly and concisely describe the problem or feature (this cannot be empty).
4
-
5
- ### Root cause
6
-
7
- Briefly describe the root cause and analysis of the problem.
8
- If there is an internal discussion on the forum, provide the link.
9
- ### Reason for not identifying earlier
10
-
11
- 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.
12
-
13
- - [ ] Guidelines/documents are not followed
14
-
15
- - Common guidelines / Core team guideline
16
- - Specification document
17
- - Requirement document
18
-
19
- - [ ] Guidelines/documents are not given
20
-
21
-
22
- - Common guidelines / Core team guideline
23
- - Specification document
24
- - Requirement document
25
-
26
-
27
- ### Reason:
28
- Mention any one or more reasons from the above points.
29
-
30
- ### Action taken:
31
- What action did you take to avoid this in future?
32
-
33
- ### Related areas:
34
- Is there any other related areas also to be addressed?
35
-
36
-
37
- ### Is it a breaking issue?
38
-
39
- If it is a breaking issue, provide the commit detail which caused this break.
40
-
41
- ### Solution description
42
-
43
- Describe your code changes in detail for reviewers.
44
-
45
- ### Output screenshots
46
-
47
- Post the output screenshots if an UI is affected or added due to this bug.
48
- ### Areas affected and ensured
49
-
50
- List the areas affected by your code changes.
51
-
52
- ### Additional checklist
53
- This may vary for different teams or products. Check with your scrum masters.
54
-
55
- - Did you run the automation against your fix?
56
- - Is there any API name change?
57
- - Is there any existing behavior change of other features due to this code change?
58
- - Does your new code introduce new warnings or binding errors?
59
- - Does your code pass all FxCop and StyleCop rules?
60
- - Did you record this case in the unit test or UI test?
@@ -1,42 +0,0 @@
1
- ### Feature description
2
-
3
- Clearly and concisely describe the problem or feature (this cannot be empty).
4
-
5
- ### Analysis and design
6
-
7
- If there is an external design, link to its project documentation area.
8
- If there is an internal discussion on the forum, provide the link.
9
- ### Solution description
10
-
11
- Describe your code changes in detail for reviewers.
12
-
13
- ### Output screenshots
14
-
15
- Post the output screenshots if an UI is affected or added due to this feature.
16
- ### Areas affected and ensured
17
-
18
- List the areas are affected by your code changes.
19
-
20
- ### Test cases
21
-
22
- Provide the unit testing written file details to understand the use cases considered in this implementation.
23
- 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.
24
- Provide the test cases Excel file alone if the feature cannot be automated in any case.
25
- Test bed sample location
26
-
27
- 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.
28
-
29
- ### Test bed sample location
30
-
31
- 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.
32
-
33
-
34
- ### Additional checklist
35
- This may vary for different teams or products. Check with your scrum masters.
36
-
37
- - Did you run the automation against your fix?
38
- - Is there any API name change?
39
- - Is there any existing behavior change of other features due to this code change?
40
- - Does your new code introduce new warnings or binding errors?
41
- - Does your code pass all FxCop and StyleCop rules?
42
- - Did you record this case in the unit test or UI test?