0 Fork 0

mirror of https://github.com/aphrody-labs/PowerShell.git synced 2026-10-17 20:56:02 +00:00

Files

T

Dongbo Wang 41f12b1d2c Push locals of automatic variables to 'DottedScopes' when dotting script cmdlets (#4709 )

When dotting a script cmdlet, the locals of automatic variables from the `PSScriptCmdlet` is not set up in the current scope before parameter binding. The fix is to push the locals in `CommandProcessor.OnSetCurrentScope` and pop them in `CommandProcessor.OnRestorePreviousScope`, which will be called from `SetCurrentScopeToExecutionScope` and `RestorePreviousScope` respectively.

Summary of changes:
1. When a new local scope is used, currently we set the locals for `CommandProcessor` right before parameter binding (in `BindCommandLineParametersNoValidation`); we set the locals for `ScriptCommandProcessor` in `Prepare`. I moved both to the constructor, right after the new scope is created so that the code is more consistent.

2. In `CmdletParameterBinderController.cs`, we set up the `PSBoundParameters` and `MyInvocation` variables in `HandleCommandLineDynamicParameters` again, which I think is unnecessary because this method is only called from `BindCommandLineParametersNoValidation`, where the setup is done for the first time.

3. Currently, the locals will be set for dotted script cmdlet in `EnterScope()` and `ExitScope()`. Now, that logic is moved to `OnSetCurrentScope` and `OnRestorePreviousScope` of `CommandProcessor`. This not only makes sure that locals are set before parameter binding, but also is consistent with the `ScriptCommandProcessor`.

2017-09-06 10:25:33 -07:00

common/markdown

Update docs about the pull-request-process (#4710 )

2017-09-04 10:29:20 -07:00

csharp

Move powershell to 2.0.0-preview3-25426-01 using the .NET CLI 2.0.0-preview2-006502 (#4144 )

2017-06-30 13:07:14 -07:00

docker/networktest

PSScriptAnalyzer fixes by category (#4261 )

2017-07-21 21:03:49 -07:00

powershell

Push locals of automatic variables to 'DottedScopes' when dotting script cmdlets (#4709 )

2017-09-06 10:25:33 -07:00

PSReadLine

Move powershell to 2.0.0-preview3-25426-01 using the .NET CLI 2.0.0-preview2-006502 (#4144 )

2017-06-30 13:07:14 -07:00

shebang

Reorganize tests

2016-01-14 17:00:06 -08:00

tools

Report the same number of tests when run by Travis via cron (#4731 )

2017-08-31 15:03:20 -07:00

README.md

Add test/README.md

2016-03-30 23:30:26 -07:00

Test.Common.props

Move to the official .NET Core 2.0 (#4603 )

2017-08-16 17:32:46 -07:00

README.md

Testing

The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./csharp. The sanity tests for the Full .NET build of PowerShell are in ./fullclr, and the third-party shebang test is in ./shebang.