Skip to content
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

Left Justification option for summary table columns #1995

Closed
erichiller opened this issue Apr 17, 2022 · 1 comment · Fixed by #2410
Closed

Left Justification option for summary table columns #1995

erichiller opened this issue Apr 17, 2022 · 1 comment · Fixed by #2410

Comments

@erichiller
Copy link

erichiller commented Apr 17, 2022

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:

Method                            | Metric 1
----------------------------------|-------------
MajorMinorSpecificBaseline        | 1
MajorMinorSpecificDoItOneWay      | 2
SomeVeryDifferentMinorSpecific    | 3
MajorMinorSpecificDoItAnotherWay  | 4

Rather than the current:

Method                            | Metric 1
----------------------------------|-------------
       MajorMinorSpecificBaseline | 1
     MajorMinorSpecificDoItOneWay | 2
   SomeVeryDifferentMinorSpecific | 3
 MajorMinorSpecificDoItAnotherWay | 4

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:

@adamsitnik
Copy link
Member

@erichiller it sounds reasonable, please send a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants