Refactor route_request to reduce Cognitive Complexity#77
Conversation
…e_request Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 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. |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
This PR addresses the high cognitive complexity of the
NextjsFrontendEvaluator.route_requestmethod innextjs_frontend_simulation.pyby extracting the adjectival bounds check (_check_adjectival_bound) and target agent routing logic (_determine_target_agent) into separate private methods. The original complexity score was 11, and it has now been reduced to 3. Tests verify the functionality remains identical.PR created automatically by Jules for task 7272374631852410419 started by @projectedanx