Frontmatter
| id | 8904 |
| title | Verify Scoped Deterministic ID Generation for Functional Components |
| state | Closed |
| labels | aitestingcore |
| assignees | tobiu |
| createdAt | Jan 28, 2026, 6:19 PM |
| updatedAt | Jan 28, 2026, 6:35 PM |
| githubUrl | https://github.com/neomjs/neo/issues/8904 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | 8899 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Jan 28, 2026, 6:35 PM |
Verify Scoped Deterministic ID Generation for Functional Components
tobiu added parent issue #8899 on Jan 28, 2026, 6:19 PM

tobiu
Jan 28, 2026, 6:33 PM
Input from Gemini 3 Pro:
✦ I have added verification tests for Class-Based Component ID Generation.
Verification: Created
test/playwright/unit/component/IdGeneration.spec.mjs. Tests confirm:
- JIT Generation: Nodes without IDs get them (
neo-vnode-X).- Persistence: Auto-generated IDs persist across updates (proving
this.vdommutation works).- Dynamic Insertion: New nodes get new IDs, existing nodes remain stable.
Completion: All sub-tasks for the VDOM ID Architecture Shift are complete and verified.
- App Authority (TreeBuilder) implemented.
- Obsolete Sync logic removed.
- Functional Components (Scoped Deterministic IDs) implemented.
- Unit Tests stabilized and expanded.
tobiu assigned to @tobiu on Jan 28, 2026, 6:35 PM
tobiu closed this issue on Jan 28, 2026, 6:35 PM
Objective: Explicitly verify the "Scoped Deterministic ID Generation" logic introduced in Ticket #8903 to ensure it behaves as designed, particularly regarding the "Shielding" effect of custom IDs.
Tasks:
test/playwright/unit/functional/IdGeneration.spec.mjs.cmp-1__0,cmp-1__1, etc.).id="my-scope") -> Child.my-scope__0.my-scope__0), proving they are shielded from the parent's index shift.Why: To catch regressions in the ID generation logic that might cause unnecessary DOM thrashing (full re-renders) in complex Functional Components.