You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful if there was an option to align/justify the Method column (leftmost column when there's only one namespace and It would be useful if there was an option to align/justify the Method column (leftmost column when there's only one namespace and class). My use case is that I typically name my methods in order of increasing specificity (opposite of DNS).
With left justification, the bases are aligned which makes it easier for me to quickly scan the column and see what methods are similar. Whereas with right justification there is no alignment between names at all.
My thought was adding something like DefaultTextColumnJustification to SummaryStyle with a type of TextJustification.
From a brief glance, I think the following would need to change:
It would be useful if there was an option to align/justify the Method column (leftmost column when there's only one namespace and It would be useful if there was an option to align/justify the Method column (leftmost column when there's only one namespace and class). My use case is that I typically name my methods in order of increasing specificity (opposite of DNS).
eg. this:
Rather than the current:
With left justification, the bases are aligned which makes it easier for me to quickly scan the column and see what methods are similar. Whereas with right justification there is no alignment between names at all.
My thought was adding something like
DefaultTextColumnJustification
toSummaryStyle
with a type ofTextJustification
.From a brief glance, I think the following would need to change:
SummaryTableColumn
has aJustify
property, but it is set by whether the inputIColumn
is text or numeric, as there's no justify property onIColumn
SummaryTable
could pass the newDefaultTextColumnJustification
fromSummaryStyle
toSummaryTableColumn
hereThe text was updated successfully, but these errors were encountered: