-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Split subtask approval settings #2482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,41 @@ | ||
| import * as vscode from "vscode" | ||
|
|
||
| /** | ||
| * Migrates old subtasks setting to new subtaskCreation and subtaskCompletion settings. | ||
| * | ||
| * TODO: Remove this migration code in September 2025 (6 months after implementation) | ||
| */ | ||
| export async function migrateSubtasksSettings( | ||
| context: vscode.ExtensionContext, | ||
| outputChannel: vscode.OutputChannel, | ||
| ): Promise<void> { | ||
| // Old and new setting keys | ||
| const subtasksKey = "alwaysAllowSubtasks" | ||
| const subtaskCreationKey = "alwaysAllowSubtaskCreation" | ||
| const subtaskCompletionKey = "alwaysAllowSubtaskCompletion" | ||
|
|
||
| try { | ||
| // Get old value | ||
| const oldValue = await context.globalState.get(subtasksKey) | ||
|
|
||
| if (oldValue !== undefined && typeof oldValue === "boolean") { | ||
| // Update new settings | ||
| await Promise.all([ | ||
| context.globalState.update(subtaskCreationKey, oldValue), | ||
| context.globalState.update(subtaskCompletionKey, oldValue), | ||
| ]) | ||
|
|
||
| // Schedule cleanup | ||
| setTimeout(async () => { | ||
| try { | ||
| await context.globalState.update(subtasksKey, undefined) | ||
| outputChannel.appendLine("Migrated subtasks settings") | ||
| } catch (error) { | ||
| outputChannel.appendLine(`Failed to delete old subtasks setting: ${error}`) | ||
| } | ||
| }, 0) | ||
| } | ||
| } catch (error) { | ||
| outputChannel.appendLine(`Migrating subtasks settings failed: ${error}`) | ||
| } | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only feedback on this - I wonder if we should stick to the
alwaysAllowSubtaskskey for the creation, and preserve their current setting. Otherwise the settings are going to get cleared out for everyone right?I guess we could also add migration logic that sets the value of both new keys to the value of the old key - that might not be so bad. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initially I didn't change it for the same reason, but as I was working on it I thought it would be important to maintain clarity in the code going forward (already too many references to "subtasks".)
Adding some migration logic I suppose would be easy, just have no idea where exactly to put it. Even easier would be to just put a notice in the changelog that this setting will now be reset to defaults and people should double check their config after the update. People do read changelogs, right? That way there's no need to leave some migration code hanging around.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think people read in general :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do have a migrateSettings method called from extension.ts