CodingTraker used to record the timestamps of refactorings incorrectly during a short period of time (See issue #237). As a consequence of this bug, the timestamp of NewStartedRefactoringOperation may be -1. Therefore, every client of CodingTracker that relies on the timestamp of NewStartedRefactoringOperation has to handle the incorrect timestamps. It would be nice if we could fix the problem once for all the clients of CodingTracker.
@Wanderer777: Given that the incorrect timestamps of NewStartedRefactoringOperation are not prevalent, will you be able to fix them manually?
CodingTraker used to record the timestamps of refactorings incorrectly during a short period of time (See issue #237). As a consequence of this bug, the timestamp of
NewStartedRefactoringOperation
may be -1. Therefore, every client of CodingTracker that relies on the timestamp ofNewStartedRefactoringOperation
has to handle the incorrect timestamps. It would be nice if we could fix the problem once for all the clients of CodingTracker.@Wanderer777: Given that the incorrect timestamps of
NewStartedRefactoringOperation
are not prevalent, will you be able to fix them manually?