Repository navigation
🧹 [code health] Refactor Remove-StartupEntry to reduce cyclomatic complexity - #57
Conversation
- Extract Get-MatchedStartupEntries helper function in unslop-win11.ps1 and unslop-win10.ps1. - Consolidate runKey iteration and reduce nesting depth in Remove-StartupEntry. - Preserve all registry backup, restore, dry-run and error trapping behaviors.
|
👋 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. |
…re() and pre-compiled regex
🎯 What:
Refactored
Remove-StartupEntryinunslop-win11.ps1andunslop-win10.ps1by extracting property retrieval and filtering intoGet-MatchedStartupEntriesand unifying runKey loop control flow.💡 Why:
Reduces high cyclomatic complexity and nesting depth in
Remove-StartupEntryto improve readability and maintainability while preserving ADR-022 architectural isolation and 100% restoration symmetry.✅ Verification:
Test-MasterGate.ps1 -Fast(AST parser clean, 0 PSScriptAnalyzer warnings/errors, 0 merge conflict markers).✨ Result:
Lower complexity, cleaner structure, zero behavioral changes.
PR created automatically by Jules for task 17385465595261459286 started by @Ahmed-Yaseen99