@immense/vue-pom-generator 1.0.76 → 1.0.77
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/RELEASE_NOTES.md +44 -37
- package/dist/index.cjs +2 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.mjs +2 -1
- package/dist/index.mjs.map +1 -1
- package/dist/transform.d.ts.map +1 -1
- package/package.json +1 -1
package/RELEASE_NOTES.md
CHANGED
|
@@ -1,63 +1,70 @@
|
|
|
1
|
-
I'll
|
|
2
|
-
|
|
1
|
+
I'll investigate the actual repository state to understand the full scope of changes between v1.0.76
|
|
2
|
+
and HEAD.
|
|
3
3
|
|
|
4
|
-
Let me
|
|
4
|
+
Let me check the tag timing and PR merge dates to understand which PRs are actually new in this
|
|
5
|
+
release.
|
|
5
6
|
|
|
6
|
-
|
|
7
|
-
|
|
7
|
+
Now I understand - v1.0.76 was tagged at 2026-07-28T17:02:36-05:00 (start of window) and HEAD is at
|
|
8
|
+
2026-07-29T07:09:25-05:00 (end of window). Let me verify which PRs were actually merged in this
|
|
9
|
+
window.
|
|
8
10
|
|
|
9
|
-
|
|
10
|
-
UTC). All other PRs were merged days/weeks/months earlier. Let me check the git history to confirm
|
|
11
|
-
what's actually between v1.0.75 and HEAD.
|
|
11
|
+
Let me verify the merge times of key PRs to confirm which are actually in this release window.
|
|
12
12
|
|
|
13
|
-
|
|
14
|
-
all repo PRs, not just this release's. Let me read the actual changed files to write accurate
|
|
15
|
-
notes.
|
|
13
|
+
Now I have clear evidence. Only PR #36 is new in this release:
|
|
16
14
|
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
15
|
+
- #36 (e5b00f4): 2026-07-29T07:09:25-05:00 = HEAD (end of window)
|
|
16
|
+
- #35 (28e58a2): 2026-07-28T17:02:36-05:00 = v1.0.76 (start of window)
|
|
17
|
+
- #34 and earlier: all before the window start
|
|
20
18
|
|
|
21
|
-
|
|
22
|
-
|
|
19
|
+
Let me examine the actual diff to write accurate release notes.
|
|
20
|
+
|
|
21
|
+
Now I have a complete understanding. Let me also check the PR #36 description for additional
|
|
22
|
+
context.
|
|
23
|
+
|
|
24
|
+
I now have all the information needed. The git evidence is conclusive:
|
|
25
|
+
|
|
26
|
+
- v1.0.76 was tagged at commit #35 (2026-07-28T17:02:36-05:00)
|
|
27
|
+
- HEAD is commit #36 (2026-07-29T07:09:25-05:00)
|
|
28
|
+
- Only PR #36 is in the v1.0.76..HEAD range
|
|
29
|
+
- All other listed PRs (#1–#35) were already released in prior versions
|
|
30
|
+
|
|
31
|
+
Here are the release notes:
|
|
23
32
|
|
|
24
33
|
Highlights
|
|
25
34
|
|
|
26
|
-
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
files.
|
|
30
|
-
- Flags page-level selector/evaluation APIs (page.click, page.evaluate, page.waitForSelector,
|
|
31
|
-
page.$eval, page.$$eval, page.isHidden, page.isVisible).
|
|
32
|
-
- Detects legacy animateCursor* helper calls and reports them with a dedicated message.
|
|
33
|
-
- Rule is scoped to spec files only (.spec.ts/.tsx, .spec.js/.jsx); non-spec files are unaffected.
|
|
34
|
-
- Registered and exported from the ESLint plugin entry point alongside existing rules.
|
|
35
|
+
- Slot-scope key detection now traverses v-if wrappers — scoped-slot data objects wrapped in
|
|
36
|
+
v-if/v-for branches no longer lose their stable keyed test IDs, ensuring generated POM locators
|
|
37
|
+
remain consistent across conditional rendering boundaries.
|
|
38
|
+
- Minimal, surgical release: 1 PR, 2 files changed (+56 / −1).
|
|
35
39
|
|
|
36
40
|
Changes
|
|
37
41
|
|
|
38
|
-
|
|
42
|
+
Transform
|
|
39
43
|
|
|
40
|
-
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
+
- Preserve element-to-element hierarchy through non-element wrappers — when an element's immediate
|
|
45
|
+
parent is a non-element node (IF_BRANCH, FOR, IF), the transform now falls back to
|
|
46
|
+
context.grandParent to maintain the correct parent chain in the hierarchy map (transform.ts).
|
|
47
|
+
- This ensures slot-scope and v-for key detection can walk past v-if/v-for wrappers to find the
|
|
48
|
+
enclosing <template> or v-for element, producing stable keyed test IDs such as
|
|
49
|
+
`MyComp-${maintenanceItem.key ?? ...}-MoveToTop-button`.
|
|
44
50
|
|
|
45
51
|
Tests
|
|
46
52
|
|
|
47
|
-
- Added test
|
|
48
|
-
|
|
53
|
+
- Added regression test verifying stable keyed test IDs for scoped-slot data objects through v-if
|
|
54
|
+
wrappers.
|
|
55
|
+
- Added regression test verifying stable keyed test IDs for scoped-slot data objects destructured
|
|
56
|
+
with an explicit key prop.
|
|
49
57
|
|
|
50
58
|
Breaking Changes
|
|
51
59
|
|
|
52
|
-
None.
|
|
60
|
+
None.
|
|
53
61
|
|
|
54
62
|
Pull Requests Included
|
|
55
63
|
|
|
56
|
-
- ]8;id=md-
|
|
64
|
+
- ]8;id=md-1g29ijb;https://github.com/immense/vue-pom-generator/pull/36#36 — fix: preserve slot-scope key detection through v-if wrappers]8;;]8;; (@dkattan)]8;;
|
|
57
65
|
|
|
58
66
|
Testing
|
|
59
67
|
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
selector APIs. No existing tests were modified beyond the import addition.
|
|
68
|
+
Two new unit tests were added to tests/transform.test.ts covering scoped-slot key detection through
|
|
69
|
+
v-if wrappers and explicit key prop destructuring. No existing tests were modified.
|
|
63
70
|
|
package/dist/index.cjs
CHANGED
|
@@ -7357,7 +7357,8 @@ function createTestIdTransform(componentName, componentHierarchyMap, nativeWrapp
|
|
|
7357
7357
|
(p) => p.type === compilerCore.NodeTypes.DIRECTIVE && p.name === "bind" && p.arg?.type === compilerCore.NodeTypes.SIMPLE_EXPRESSION && p.arg.content === testIdAttribute && !!p.exp
|
|
7358
7358
|
);
|
|
7359
7359
|
}
|
|
7360
|
-
const
|
|
7360
|
+
const grandParent = context.grandParent;
|
|
7361
|
+
const parentElement = !parentIsRoot && context?.parent?.type === compilerCore.NodeTypes.ELEMENT ? context.parent : !parentIsRoot && grandParent?.type === compilerCore.NodeTypes.ELEMENT ? grandParent : null;
|
|
7361
7362
|
hierarchyMap.set(element, parentElement);
|
|
7362
7363
|
const normalizeFilePath = (filePath) => path.normalize(safeRealpath2(path.resolve(filePath)));
|
|
7363
7364
|
const normalizedFilePath = normalizeFilePath(context.filename);
|