Add configuration option to control QuickPick Esc behavior #63
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR addresses the issue where pressing "Esc" on the QuickPick panel unintentionally clears all checkboxes, which can be problematic for task management workflows.
Problem
When users press "Esc" to exit the QuickPick panel, the extension treats this as selecting no items and proceeds to uncheck all existing checkboxes. This behavior can be frustrating and destructive for users who accidentally press Esc or expect it to simply cancel the operation without making changes.
Solution
Added a new configuration option
markdown-checkbox.quickPickEscBehaviorthat allows users to control what happens when Esc is pressed:"doNothing"(default): Preserves the current state of all checkboxes when Esc is pressed"uncheckAll": Maintains the previous behavior for users who prefer itChanges Made
Configuration
Logic Update
The
handleQuickPickActionsfunction now checks if the user pressed Esc (items === undefined) and respects the configuration:Backward Compatibility
The change is fully backward compatible. The default behavior is now safer (
"doNothing"), but users who prefer the original behavior can easily switch to"uncheckAll"in their settings.Testing
Fixes #62.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
update.code.visualstudio.comnode ./out/test/runTest.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.