Closed nevrome closed 1 year ago
Base: 70.96% // Head: 70.93% // Decreases project coverage by -0.03%
:warning:
Coverage data is based on head (
ecb03d7
) compared to base (fda9e36
). Patch coverage: 82.50% of modified lines in pull request are covered.
:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Right - my biggest concern is that JannoFile
doesn't really capture the meaning. It's just an arbitrary list of JannoRow
s. I considered naming it JannoSet
, but a set has no order. JannoList
is already in use. Do you have a suggestion?
I replaced all instances of [JannoRow]
to make sure that it becomes harder to accidentally run into the issue I describe in #229. But I understand that it looks a bit weird at times, not least because of the type name.
Yes, the name isn't perfect. You could have used JannoMonoid
, but that's not a name you want everywhere. What about JannoRows
?
JannoRows
is simple and clear. I love it. Will use that. Thanks!
Here's an implementation of the idea shared in #229