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
I was testing the latest version of the action, and it looks amazing, however, depending on the size of the project, the output of the coverage and the lines in one could be tooo long. Like on the following example (page on 40% of zoom):
So, I would like to suggest breaking the single report output. One for the coverage and the other for the lines. That would allow people to choose when and how they want to expose this information in the PR.
What do you think?
Cheers!
The text was updated successfully, but these errors were encountered:
i was thinking to add custom markdown formatting of report gh output variable to have some fancy things, like collapsible sections. then uncovered lines could be enclosed in individual section so users can show/hide it separately.
I think that you will only be able to do this if you add a feature to your action to comment itself on the PR, this gives you the freedom to manipulate the format of the PR.
Because, manipulating the structure from a json to markdown, it will be tricky. I would go for breaking in smaller outputs and leaving the user to manipulate and format the markdown as it wishes.
Hey, it's me again xD
I was testing the latest version of the action, and it looks amazing, however, depending on the size of the project, the output of the coverage and the lines in one could be tooo long. Like on the following example (page on 40% of zoom):
So, I would like to suggest breaking the single
report
output. One for the coverage and the other for the lines. That would allow people to choose when and how they want to expose this information in the PR.What do you think?
Cheers!
The text was updated successfully, but these errors were encountered: