WIP: Test cherry pick #1801
Closed
WIP: Test cherry pick #1801
Conversation
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
* Prep 1.11 release with Changelog * change default branch to prevent using the wrong branch * spaces
* turn off non-windows gate for attach to process * address feedback * no single quotes
* Work with comma separated exclude filter * Add a filter... * Adjust filter. Remove case sensetivity. * Change Exclude Fitler to array.
…werShell#1729) (PowerShell#1754) * Handle describe block strings with single quotes inside it. * fix replace call to handle expression with more than one single quote as well
* Update build to clear node modules Add removal of the node_modules directory on Clean task. Move condition for restore to the build prerequisite. This allows the restoring of node modules even if the folder exists. * Don't remove node_modules. This causes bad things to happen when you're editing in vscode (@types is locked until code exits) Next best thing might be to npm prune (or maybe npm install?) * npm install keeps putting these spaces in...
* Check that item has a Name property * Update src/features/ShowHelp.ts Do a truthy check instead. Co-Authored-By: corbob <[email protected]>
…erShell#1746) I don't think we should merge this to v1.x. I want to take the opportunity with the preview to make sure package.json name prop change to "powershell" doesn't cause any problems. This addresses issue caused w/LiveShare ext loaded and you try to debug. While this issue has been fixed by a mod to the next verson of VSCode, we should have our debugger configured properly. See microsoft/vscode#61649 Also, made debug snippet prop order consistent: name, type, request.
Update session menu "switch to" entries to more clearly distinguish the "version name". Fix PowerShell#1734
…rShell#1764) * Added Calculated Property and ShouldProcess Snippets * Added Pester Describe, Context & It Snippets * Placeholder Rename for calc property snippet * Fixed description for Calculated Property * Calc Property Enhanced Description Co-Authored-By: brettmillerb <[email protected]> * Amended the tab stop for calc-property to include .
…werShell#1776) * Migrate Pester version detection into an InovkePester stub script * Move TestName warning into script * Improve stub script, move module loaded check to beginning * Address Codacy issue * Address PR feedback * Move TestName check before LineNumber in case of multiple blocks/line
* Add Debug Runspace command * Update package.json based on feedback. * Update response to match PSES response. * Change how we ask for RunspaceId. * Clean up.
|
this should go into legacy |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I am waiting on #1800 before this goes in