-
Notifications
You must be signed in to change notification settings - Fork 697
[vscode-shared] Add outputMarker option to runWorkspaceCommandAsync #5590
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
434838d
Initial plan
Copilot 8b7934f
Refactor string marker logic into runWorkspaceCommandAsync
Copilot 82b974e
Address code review: use indexOf instead of lastIndexOf for marker se…
Copilot a76b3cc
Refactor outputMarker to only extract from output, not construct command
Copilot 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
Some comments aren't visible on the classic Files Changed page.
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,14 +5,37 @@ import { ITerminal } from '@rushstack/terminal'; | |
| import * as vscode from 'vscode'; | ||
| import { stripVTControlCharacters } from 'node:util'; | ||
|
|
||
| /** | ||
| * Options for extracting a specific value from the command output using markers. | ||
| * When provided, the function will search for the markers in the command output and | ||
| * return only the content between them. This is useful for extracting specific | ||
| * values from shell output that may contain additional noise. | ||
| */ | ||
| export interface IOutputMarkerOptions { | ||
| /** | ||
| * The prefix marker used to identify the start of the desired output. | ||
| */ | ||
| prefix: string; | ||
| /** | ||
| * The suffix marker used to identify the end of the desired output. | ||
| */ | ||
| suffix: string; | ||
| } | ||
|
|
||
| export async function runWorkspaceCommandAsync({ | ||
| terminalOptions, | ||
| commandLine, | ||
| terminal | ||
| terminal, | ||
| outputMarker | ||
| }: { | ||
| terminalOptions: vscode.TerminalOptions; | ||
| commandLine: string; | ||
| terminal: ITerminal; | ||
| /** | ||
| * Optional marker options for extracting specific output from the command result. | ||
| * When provided, the returned output will be only the content between the markers. | ||
| */ | ||
| outputMarker?: IOutputMarkerOptions; | ||
| }): Promise<string> { | ||
| const vsTerminal: vscode.Terminal = vscode.window.createTerminal(terminalOptions); | ||
|
|
||
|
|
@@ -66,7 +89,21 @@ export async function runWorkspaceCommandAsync({ | |
| startExecutionDisposable.dispose(); | ||
|
|
||
| if (event.exitCode === 0) { | ||
| resolve(outputStream); | ||
| // If outputMarker was provided, extract the content between markers | ||
| if (outputMarker) { | ||
| const startIndex: number = outputStream.indexOf(outputMarker.prefix); | ||
| const endIndex: number = outputStream.indexOf(outputMarker.suffix); | ||
|
Comment on lines
+94
to
+95
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Per prior conversation regarding the debug certificate manager, to deal with some shells that echo the command to be run, we should be using |
||
| if (startIndex !== -1 && endIndex !== -1 && endIndex > startIndex) { | ||
| const extractedOutput: string = outputStream | ||
| .substring(startIndex + outputMarker.prefix.length, endIndex) | ||
| .trim(); | ||
| resolve(extractedOutput); | ||
| } else { | ||
| reject(new Error('Failed to parse output from command: markers not found')); | ||
| } | ||
| } else { | ||
| resolve(outputStream); | ||
| } | ||
| } else { | ||
| reject(outputStream); | ||
| } | ||
|
|
||
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.
Need to explicitly define the behavior when the markers appear multiple times.