aglinxinyuan opened a new pull request, #7442:
URL: https://github.com/apache/texera/pull/7442
### What changes were proposed in this PR?
The suite builds the category map and never renders it, so everything the
template decides was unpinned.
Adds 10 tests. The one with real teeth is the jump-to-operator shortcut,
guarded by two conditions: it is withheld for the `unknown operator` sentinel,
which would navigate the canvas to nothing, and for the operator already being
shown, where it would be a no-op. Its click also stops propagation — the icon
sits in the collapse header and would otherwise toggle the panel underneath the
user.
Also covers the all-operators banner appearing only for an unscoped frame,
the empty state appearing only when there is nothing to report, the grouping
into category headings, and the message heading the panel with the details in
its body.
**Verified by mutation**, all reverted (template diff empty):
| Mutation | Result |
|---|---|
| show the all-operators banner always | red |
| show the empty state always | red |
| head the category with its size instead of its name | red |
| head the panel with the details | red |
| put the message in the body | red |
| offer the jump for the unknown-operator sentinel | red |
| offer the jump for the operator already shown | red |
| jump to the frame's operator instead of the error's | red |
| drop `stopPropagation` from the jump | red |
The empty-state mutation **survived its first run**: the test asserted the
message appears with no errors but never that it disappears once there are
some. It now checks both directions.
No production file is touched.
### Any related issues, documentation, discussions?
Closes #7439
### How was this PR tested?
```
npx ng test --watch=false --include="**/error-frame.component.spec.ts"
```
```
Test Files 1 passed (1)
Tests 17 passed (17)
```
10 new on top of the existing 7. `yarn format:ci` passes.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 5)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
