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
{{ message }}
This repository has been archived by the owner on Jul 15, 2020. It is now read-only.
When working with a namespaced codebase, the tool is of limited use. Here are some examples:
Renaming Exception to RenamedException changes too much (i.e. all Exception classes, but not all that's needed, so that class Exception extends \TYPO3\Fluid\Core\Exception becomes class RenamedException extends \TYPO3\Fluid\Core\Exception.
Using fully qualified class names matches only uses in docblocks, it seems. At least fully qualified use in code is left unchanged.
What should happen, is that renaming Some\Namespaced\Class to Some\Namespaced\DifferentName should just work. :)
The text was updated successfully, but these errors were encountered:
Agree, this would be very nice. Unfortunately, I'm not putting a lot of time into Scisr development at this point. I'd definitely accept a pull request, though :)
When working with a namespaced codebase, the tool is of limited use. Here are some examples:
Renaming
Exception
toRenamedException
changes too much (i.e. allException
classes, but not all that's needed, so thatclass Exception extends \TYPO3\Fluid\Core\Exception
becomesclass RenamedException extends \TYPO3\Fluid\Core\Exception
.Using fully qualified class names matches only uses in docblocks, it seems. At least fully qualified use in code is left unchanged.
What should happen, is that renaming
Some\Namespaced\Class
toSome\Namespaced\DifferentName
should just work. :)The text was updated successfully, but these errors were encountered: