@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 CHANGED
@@ -1,63 +1,70 @@
1
- I'll verify which PRs actually fall in the stated merge window by checking their merge timestamps
2
- against the GitHub API, since the diff only shows one commit but many PRs are listed.
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 try fetching PR data via the web_fetch tool.
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
- PR #35 merged at 22:02:36Z. The window in UTC is 21:58:43Z–22:02:36Z. Let me check the other PRs'
7
- merge times to see which actually fall in this window.
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
- Only PR #35 (22:02:36Z) and PR #34 (21:58:43Z) have merge times near the window (21:58:43Z–22:02:36Z
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
- v1.0.75 points to the merge of PR #34. So v1.0.76 = v1.0.75 + PR #35 only. The long PR list includes
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
- I now have full context. v1.0.76 contains only PR #35 (the v1.0.75 tag is the merge of PR #34, so
18
- #34 and all earlier PRs belong to prior releases). Let me quickly check the test additions to
19
- accurately describe coverage.
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
- I have everything I need. v1.0.76 contains exactly one PR (#35); all other listed PRs belong to
22
- prior releases (v1.0.75 tag = merge of #34). Here are the release notes:
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
- - New no-raw-playwright-apis ESLint rule — bans direct use of raw Playwright APIs in spec files,
27
- steering authors toward generated fixtures/POMs or custom POMs.
28
- - Flags raw locator query APIs (locator, getByRole, getByText, getByLabel) called anywhere in spec
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
- ESLint rules
42
+ Transform
39
43
 
40
- - Added eslint/no-raw-playwright-apis.ts — a new problem-type rule that reports raw Playwright API
41
- usage in spec files, encouraging generated POM methods instead.
42
- - Registered the rule as "no-raw-playwright-apis" in the plugin's rules map and exported
43
- noRawPlaywrightApisRule from eslint/index.ts.
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 coverage for the new rule in tests/eslint.test.ts, covering valid POM usage, non-spec
48
- file exemption, animateCursor detection, raw locator query APIs, and direct page selector APIs.
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. The new rule is opt-in and must be explicitly enabled in a consumer's ESLint config.
60
+ None.
53
61
 
54
62
  Pull Requests Included
55
63
 
56
- - ]8;id=md-1gc948a;https://github.com/immense/vue-pom-generator/pull/35#35 — feat: add no-raw-playwright-apis ESLint rule]8;;]8;; (by @dkattan)]8;;
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
- New RuleTester cases were added for no-raw-playwright-apis covering valid generated-fixture usage,
61
- non-spec file exemption, legacy cursor helper detection, raw locator queries, and direct page
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 parentElement = !parentIsRoot && context?.parent?.type === compilerCore.NodeTypes.ELEMENT ? context.parent : null;
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);