xaml-coding-guidelines
xaml-coding-guidelines copied to clipboard
XA2004, how specific should you get?
XA2004 states that you should not suffix control names with too specific types, but it does not specify how specific you should be.
For example, in the explanation, it says that a StackPanel
can be called ActionPanel
if all we are changing is its Visibility
. But Visibility
is a property of UIElement
, so why not ActionUIElement
?
I'm playing devil's advocate here, but maybe this rule or another should give a hint as to how name the control without being either too specific or to general unnecessarily.
Absolutely ! We should refine that rule to be more specific.
My guess is that naming this element ActionUIElement
will not be really useful...
If you have an idea, post a comment :)