hutiefang76 opened a new pull request, #4414:
URL: https://github.com/apache/amoro/pull/4414

   ## Why are the changes needed?
   Rapid typing currently schedules one search per input event. Table and 
database searches should each send only the final keyword after 300ms, and 
pending callbacks should stop when the component unmounts.
   
   Fixes #4411.
   
   ## Brief change log
   - Keep independent search timers per component and cancel pending callbacks 
on unmount.
   - Preserve callback arguments and allow debounce reuse after cancellation.
   
   ## How was this patch tested?
   - [x] Add test cases: five tests compile and mount the actual Vue setup, 
covering rapid input, clear, independent fields/instances, unmount and helper 
reuse. Base: 5 failures; fixed: 5 passes.
   - [x] Run tests locally: preload recovery test, affected ESLint checks and 
Vite production build pass. Full vue-tsc reports the same nine pre-existing 
errors as the pristine base.
   - [ ] Add screenshots for manual tests if appropriate: no rendering change; 
no browser QA performed.
   
   ## Documentation
   - Does this pull request introduce a new feature? no
   - If yes, how is the feature documented? not applicable
   
   ## Post-Deploy Monitoring & Validation
   During the first dashboard check after deployment, an AMS maintainer should 
type rapidly, clear each field and leave the view before 300ms. The browser 
Network panel should show one request for the final keyword per field and no 
request from a timer cancelled before it runs. Existing in-flight requests are 
outside this change. Restore the previous build if valid searches stop 
returning expected lists. No project-specific alert or dashboard is assumed.
   
   ---
   
   [![Compound 
Engineering](https://img.shields.io/badge/Built_with-Compound_Engineering-6366f1)](https://github.com/EveryInc/compound-engineering-plugin)
   


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