| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
Can you please respond to me comment above? |
Sorry, something went wrong.
|
Please add a test |
Sorry, something went wrong.
|
Chunqing Chen (@chunqingchen) Please update this PR with tests per Steve Lee (@SteveL-MSFT) 's request |
Sorry, something went wrong.
|
Chunqing Chen (@chunqingchen) Please use a meaningful title and description for the PR. The current title and description is suitable for an issue but not for a PR.
|
Sorry, something went wrong.
There was a problem hiding this comment.
Please use $helpContent | Should Not Be $null
Sorry, something went wrong.
There was a problem hiding this comment.
corrected
Sorry, something went wrong.
There was a problem hiding this comment.
Please add new line.
Sorry, something went wrong.
There was a problem hiding this comment.
Please make the title more informative for the test.
Sample - "Get-Help in JEA sessions".
Sorry, something went wrong.
There was a problem hiding this comment.
the test suite contains different bug fixes for JEA sessions. The information is contained in each test itself. thank you.
Sorry, something went wrong.
There was a problem hiding this comment.
I believe that we should not mention "bug fixes" in the title and it is better to make comments in It blocks with a link to the bug number below.
# Fix #1234567890
Sorry, something went wrong.
There was a problem hiding this comment.
Please use correct case and replace -force with -Force.
Sorry, something went wrong.
There was a problem hiding this comment.
corrected
Sorry, something went wrong.
|
Ilya (@iSazonov) your comment has been resolved. thank you |
Sorry, something went wrong.
There was a problem hiding this comment.
What is the user experience with this change? With this change does help still appear for cmdlets that are available in the JEA session? Please always include a description of the change along rationale for the change and any modification in experience.
With this change we now no longer throw a PathNotFound exception. How does this affect non-JEA sessions when the path cannot be resolved? Is it Ok to suppress the exception in this case?
Sorry, something went wrong.
There was a problem hiding this comment.
Strange but my previous comment no longer appears. Anyway my concern with this change is that previously an exception was thrown if the resolvedProviderPath is null, but now it continues. This feels like a breaking change since it now can return incomplete help for non-JEA sessions. I am not sure if that is a big deal but maybe it would be possible to detect JEA session before skipping the error.
Sorry, something went wrong.
|
Test LGTM. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Dongbo Wang (@daxian-dbw) Hi, dongbo, can you help to merge? :) |
Sorry, something went wrong.
|
Chunqing Chen (@chunqingchen) It looks new commits were pushed after the sign-off from Ilya (@iSazonov) and Paul Higinbotham (@PaulHigin). Please work with Mike Richmond (@mirichmo) to see if further review is needed. |
Sorry, something went wrong.
|
Mike Richmond (@mirichmo) Paul Higinbotham (@PaulHigin) The additional change I made is set the test case as pending because our current test harness is not supporting Register-PSSessionConfiguration cmdlet and needs further work around. however it won't blocking the product fix. Paul, would you please confirm if you are good with this? |
Sorry, something went wrong.
|
Paul Higinbotham (@PaulHigin) Please take a look and provide an updated sign off since there were updates since the original sign off. |
Sorry, something went wrong.
There was a problem hiding this comment.
I just checked and it turns out that ExecutionContext.InitialSessionState property can be null. Please add a check for this.
Sorry, something went wrong.
There was a problem hiding this comment.
Please add check for _executionContext.InitialSessionState == null
Sorry, something went wrong.
|
Paul Higinbotham (@PaulHigin) the comment has been resolved |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Chunqing Chen (@chunqingchen) This PR has been approved, but has merge conflicts. Please resolve them and push an update. I'll merge after that. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Repro:
Expected behavior:
Help content is returned for the "Select-Object" cmdlet
Actual behavior:
Cannot find path '' because it does not exist. + CategoryInfo : ObjectNotFound: (:) [Get-Help], ItemNotFoundException + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetHelpCommand