🧹 Refactor CLI options to use explicit type instead of 'any' - #9
Conversation
Defined a CliOptions interface in src/cli/index.ts to improve type safety and maintainability. Replaced the use of 'any' in handleSimpleFetch and handleTypeGeneration with the new interface. Updated runCli to use CliOptions for its local options object. Co-authored-by: sebamar88 <4359231+sebamar88@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. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
1 participant
This change improves the code health of the CLI module by replacing the explicit 'any' type for the options parameter in several functions with a well-defined
CliOptionsinterface.Key improvements:
CliOptionsinterface that captures the shape of CLI arguments (url, method, body, headers, etc.).anykeyword inhandleSimpleFetchandhandleTypeGenerationwithCliOptions & { url: string }, ensuring that the URL is present when these handlers are called.runCliwith the newCliOptionsinterface, reducing duplication.Verification:
PR created automatically by Jules for task 4561401687491474312 started by @sebamar88