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
Sometimes it's interesting to see commits, that changed contents of a particular method in a PHP class/interface/trait instead of just looking for any change in the file.
In most cases, then svn blame command with some manual input (e.g. #116) would do the trick, but in cases, when:
code was removed (therefore not shown when doing svn blame on HEAD revision)
you're not quite sure how code looked to use svn-buddy.phar search command
code to be searched is very common and used in other methods as well
How this can be implemented:
When collecting repository info from log command (aka revision log cache) for affected *.php files also:
get classes defined
do ReflectionClass to get methods
for each method do getStartLine and getEndLine
do the blame on a particular revision (or maybe svn cat or svn diff) to see if code between lines where method is declared was changed
Later accept --method option/parameter of log command, that will filter out only revisions where given method was changed.
The text was updated successfully, but these errors were encountered:
Sometimes it's interesting to see commits, that changed contents of a particular method in a PHP class/interface/trait instead of just looking for any change in the file.
In most cases, then
svn blame
command with some manual input (e.g. #116) would do the trick, but in cases, when:svn blame
on HEAD revision)svn-buddy.phar search
commandHow this can be implemented:
When collecting repository info from
log
command (aka revision log cache) for affected*.php
files also:ReflectionClass
to get methodsgetStartLine
andgetEndLine
svn cat
orsvn diff
) to see if code between lines where method is declared was changedLater accept
--method
option/parameter oflog
command, that will filter out only revisions where given method was changed.The text was updated successfully, but these errors were encountered: