Under review

Bubble up the "Favorite" property display up the hierarchy

Ariel Raunstien 7 years ago updated by Lior Kerner 5 years ago 5


class A { public B Value1;}

class B { public string Value2;}

When the quickwatch shows an instance of A - it's the type name, unless you mark field Value1 as "Favorite" (the yellow star).

However, I suggest that once you mark B.Value2 as favorite (without messing with A) - the display string for A would automatically show "Value1: { Value2: "blah blah" }"

Thank you very much for your feature request :)!

I think this suggestion would work well in certain scenarios, but in some cases, would lead to behavior that most user would consider buggy and unexpected - consider for example, if A was 'Customer' and B was 'LatestInvoice'. Just because I've marked, say, the Amount property on the Invoice class as 'starred', does not necessarily mean that the next time I view a Customer, I would be interested to see the LatestInvoice associated with it. It might, or it might not. If it's not, then this behavior would only confuse me.

Hey Omer.

I understand. However -

1) It's "overridable" - meaning that if a property of the Customer class was favorited - that would take precedence, and not show the "lower ones" (unless they would be favorited as well, naturally).

2) I do think that either way - it's better than the default string. I do think that in ANY situation - showing "LatestInvoice: { Amount = 144 }" is better than "MyApp.DAL.TooManyLayersOfAbstraction.Customer".

3) I'm not sure I instinctively understand the lifetime of the favorite selections. Are they persistent per SLN, or persistent for the current VS session, or transient, only for the current debugging session. I would argue that if it's the latter - there's no question about optimizations you could offer, since they would be gone in the next session. "Just make sure I click the least amount of buttons". If it's a more permanent option - I wouldn't mind clicking a couple of more clicks (like saying "bubble up this field in object trees visualizations").

I have something similar:

Look at property "Name"...
Just to be clear: WcContent is a interface and WcContentsManager is it's implementation...
WcContent inherits the property 'Name' from 'WcCommon' interface
Under review
Hi Carlos :)

Many apologies for the late reply and thanks for bringing this up!
This will not be included in v2.0, but we hope to incorporate it into future versions of OzCode.