Fix PlateReader filtering in machine argument selector - #135
Fix PlateReader filtering in machine argument selector#135google-labs-jules[bot] wants to merge 1 commit into
Conversation
…lector The machine argument selector used a heuristic to exclude "plate" resources (like plates, lids) from being selectable as machines. This logic incorrectly filtered out "PlateReader" if the category inference failed or was non-standard. This change refines the exclusion logic to specifically allow categories containing "reader", ensuring PlateReader requirements are always visible. Also added a unit test to verify this behavior and prevent regression.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Fixed a bug in
MachineArgumentSelectorComponentwhere "PlateReader" machine requirements were being hidden because the filtering logic aggressively excluded any category containing the string "plate".Updated the exclusion logic to allow "plate" if it also contains "reader". Added a comprehensive unit test to verify various scenarios including standard categories, fallback cases, and edge cases.
PR created automatically by Jules for task 6905719756252915550 started by @maraxen