-
Notifications
You must be signed in to change notification settings - Fork 223
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
Fix variable's 'add to watch' feature. #504
Conversation
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.
Thanks man, I'm glad to have this fixed! Also glad it was this easy :)
@@ -603,7 +603,7 @@ public VariableDetailsBase GetVariableFromExpression(string variableExpression, | |||
// of command executions into string output. However, if null is returned | |||
// then return null so that no output gets displayed. | |||
string outputString = | |||
results != null ? | |||
results != null && results.Count() > 0 ? |
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.
Possibly more efficient to use results.Any() here?
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.
Um ... yeah, good call! Much quicker than to count a 10000 element sequence.
@daviwil Before you merge a PR do you assign it a milestone or do you do that just for the related issue? |
I've been assigning milestones for both issues and PRs lately so I can keep track of what work got done. In this case since we don't have a new version number milestone yet we can just assign it to the June milestone. Once I'm ready to ship an update I scan through the closed items for the current month milestone and assign them to the specific version milestone. I should write up something about the milestone model since it's gone through several variations before I settled on this ;) |
Fix #838 in vscode-powershell