Conversation
This commit introduces a new detector for Deno, enabling `run` to automatically detect Deno projects and execute tasks defined in `deno.json` or `deno.jsonc` using `deno task`. - Added `src/detectors/deno.rs` with `DenoValidator` and `detect` function. - Updated `src/detectors/mod.rs` to register the new detector and handle `deno` ecosystem. - Added tests for detection and validation logic. - Deno detection priority is set to 5 (between Node.js and Python). - Uses `serde_json` for parsing, with graceful fallback for files with comments (JSONC).
|
👋 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. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Added support for Deno project detection and task execution.
deno.jsonanddeno.jsonc.tasksin the configuration file.deno task <command>.PR created automatically by Jules for task 7441501393502094533 started by @insign