sshiv012 opened a new pull request, #8515:
URL: https://github.com/apache/texera/pull/8515

   ### What changes were proposed in this PR?
   
   The console badges every message with its type but offers no way to act on 
it. A Python UDF that prints per tuple buries a single ERROR under its output, 
and the panel auto-scrolls, pushing it out of view.
   
   Adds a filter menu beside the settings gear: a checkbox per message type 
plus a select-all, and a line above the list reporting how many messages are 
hidden. The gear keeps the display options it already had.
   
   Each filter option carries the same badge colour as the rows it controls. 
Every type is visible by default, and a type the console has not seen before 
stays visible rather than being hidden by an unknown-type default.
   
   Both toolbar controls become buttons so the menus can be reached by keyboard 
— the settings gear could not be, as a bare `<a>` with no `href`. Verified by 
focusing the trigger and pressing Enter.
   
   ### Any related issues, documentation, discussions?
   
   Closes #8495
   
   ### How was this PR tested?
   
   42 unit tests in `console-frame.component.spec.ts`, up from 33 before this 
change.
   
   Verified live against a `1-out Python UDF` emitting 23 PRINT messages, one 
ERROR, plus COMMAND and DEBUGGER from the debug console — unticking Print 
leaves the error alone at the top.
   
   The DOM tests were checked by mutation: swapping two checkbox bindings, and 
replacing the hidden-count interpolation with a literal, each fail a test.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_016m8VBHFdnbBvNovMonAK9t


-- 
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]

Reply via email to