Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
It would be good if the check command would allow for filtering on content path. This would help in quickly identifying what is the good revision of a specific broken node in cases of very large repos.
Attaching a patch with the implementation and a few test cases to validate it in CheckValidRepositoryTest. There's a change in ConsistencyChecker regarding the place where the number of nodes and properties checked is printed. I made it in order to print those numbers before an invalid path was met (more informative and user-friendly I guess).
frm, could you take a look at it?
/cc mduerig