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
aggregateBlameAuthorModifiedAndDateInfo in FileInfoAnalyzer.java does some manual string wrangling of git blame output which is hard to interpret, contains magic numbers and breaks the git blame abstraction.
If possible, describe the solution
#2140 Introduces GitBlameLineInfo, returned by blameLine, which encapsulates this string wrangling logic. We can replace this manual string processing by using this method in aggregateBlameAuthorModifiedAndDateInfo.
The text was updated successfully, but these errors were encountered:
Hi, should we change commit-time in processGitBlameResultLine to author-time? Originally, author-time is used, and the discrepancy between author-time and commit-time has caused some test cases to fail.
I have also noticed that timestamp for author-time is in seconds. Should we change timestampMilliseconds in GitBlameLineInfo to timestampSeconds?
What feature(s) would you like to see in RepoSense
RepoSense/src/main/java/reposense/authorship/FileInfoAnalyzer.java
Lines 158 to 183 in bf78bf2
aggregateBlameAuthorModifiedAndDateInfo
inFileInfoAnalyzer.java
does some manual string wrangling of git blame output which is hard to interpret, contains magic numbers and breaks the git blame abstraction.If possible, describe the solution
#2140 Introduces
GitBlameLineInfo
, returned byblameLine
, which encapsulates this string wrangling logic. We can replace this manual string processing by using this method inaggregateBlameAuthorModifiedAndDateInfo
.The text was updated successfully, but these errors were encountered: