Skip to content

For for issue #75, variables display isn't displaying anything for ge… #76

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

Merged

Conversation

rkeithhill
Copy link
Contributor

…neric dictionaries like PSBoundParametersDictionary. Also enhanced the determination of what is expandable. We were not allowing structs like DateTime, TimeSpan and DictionaryEntry to expand. Changed test from !IsValueType to !IsPrimitive. Also enhanced the display of property values where we encounter an exception when trying to retrieve the property. Following VS debugger's lead on this on. You can see the display by looking at $Host.Runspace. And we also weren't displaying .NET properties for colletions and dictionaries. We now do that - in addition to the elements in the collection or dictionary. Also, don't try to add properties that are indexers.

@daviwil - this one is a bit more change in VariablesDetails.cs than I was anticipating. Please give it a good look over.

…ing for generic dictionaries like PSBoundParametersDictionary. Also enhanced the determination of what is expandable. We were not allowing structs like DateTime, TimeSpan and DictionaryEntry to expand. Changed test from !IsValueType to !IsPrimitive. Also enhanced the display of property values where we encounter an exception when trying to retrieve the property. Following VS debugger's lead on this on. You can see the display by looking at $Host.Runspace. And we also weren't displaying .NET properties for colletions and dictionaries. We now do that - in addition to the elements in the collection or dictionary. Also, don't try to add properties that are indexers.
// We're in the realm of regular, unwrapped .NET objects
if (dictionary != null)
{
// Buckle up kids, this is a bit weird. We could not use the LINQ
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great comment! Thanks for adding that

@daviwil
Copy link
Contributor

daviwil commented Dec 14, 2015

Excellent work yet again, thank you for carrying us through the Hack Week :)

daviwil added a commit that referenced this pull request Dec 14, 2015
…-bug

For for issue #75, variables display isn't displaying anything for ge…
@daviwil daviwil merged commit 443641c into PowerShell:master Dec 14, 2015
@rkeithhill rkeithhill deleted the rkeithhill/variable-dictionary-bug branch December 17, 2015 06:05
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
…h-filevar-fix

Fix for PowerShell#76 - launch.json now uses  as default launch path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants