Conversation
|
@rpl @willdurand I believe the improvements here are evident from my screenshots:
The only reason not to move forward with this is because it already works, albeit in this suboptimal fashion. Since I'm currently available to work on this, allow me to complete this change and merge this PR. I don’t really like keeping PRs open for years |
Rob--W
left a comment
There was a problem hiding this comment.
Thanks for improving the readability and dropping one dependency. We're willing to switch the output format.
Could you adjust the text and update the tests so that they pass?
Thanks for this, and apologies for the review delay!
|
Great, let's see if I have time this month |
|
I know we haven't been very responsive here. Should we attempt to change the output or should we drop the idea? |
|
This month I'll be a bit busy. If the changes are purely esthetic please take it over or assign Copilot to finish it up. |
ee5ffc9 to
a749197
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5426 +/- ##
==========================================
- Coverage 98.79% 98.79% -0.01%
==========================================
Files 51 51
Lines 2905 2893 -12
Branches 895 897 +2
==========================================
- Hits 2870 2858 -12
Misses 35 35 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This is obvious in the tests but it wasn't when I looked at the screenshots.. The |
|
Most likely not intentional, it should appear just after the message as in the original order. In some cases it does seem to be identical to the message so it should likely be dropped there instead of repeating it. |
|
@rpl @willdurand and I reviewed the result together. Observed changes, explicitly approved:
Requested changes to behavior:
|





Before
This isn't even the full table, it doesn't fit on my screen
After