Automate code migrations for TYPO3 Extensions
Daniel Siepmann
d3b612790c
* As sometimes not the whole token should be replaces, but only the classname within the token, we replace them always this way. * Before the refactoring, that was done in the concrete sniffs. * Affected are e.g. php doc comments. Relates: #72 |
||
---|---|---|
Documentation | ||
src | ||
tests | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
composer.json | ||
LICENSE | ||
Makefile | ||
phpcs.xml.dist | ||
phpmd.xml | ||
phpunit.xml.dist | ||
Readme.rst |
About
Our goal is to provide an automated migration for TYPO3 updates.
This should include source code modifications like adjusting old legacy class names to new ones.
The official project home page can be found at https://git.higidi.com/Automated-TYPO3-Update/automated-typo3-update . Please open new issues and merge requests there. You can login with your Github account.
Github is just used as a mirror for the project.
Check out the official documentation at: https://automated-typo3-update.readthedocs.io