Symfony2 code patch tool
This bundle has been discontinued
#Information
DHorchlerSympatchBundle consists in a tool that enables you to patch code parts anywhere in your Symfony project (including vendors). It even lets you extend foreign (vendors) entities!
Allows you to send minor code changes to your customers in just a single XML-file!
#Features:
##Get the bundle
Let Composer download and install the bundle by first adding it to your composer.json
and then running
##Enable the bundle in app/AppKernel.php
##Create the patch file(s)
use example file at Ressources/patch/patches_examples.xml to create your patch files keeping the XML structure of that file. Sympatch will look for files Ressources/patch/patches_*.xml to load the patches.
##usage:
##hints:
when specifying code locations in <beforecode> or <aftercode> tags, copy complete lines from the target source file(s) to the xml file
by running the tests any patch file in /Resources/patch like patches_.xml is temporarily renamed to patches_.xml.unittest
the use of <beforecode>, <aftercode> is encouraged over <beforeline>, <afterline> for two reasons: more than one patch in the same file will not cause problems of keeping track of line numbers because of line shifts caused by each patch. generally, chances are better to have patches working after code base upgrades without modifications.
the deactivateall command has been added to allow code base upgrades without version collisions. It will deactivate all patches disregarding the status that each patch has in the patch files. The sequence would be:
when you send code patches to others, mark the patch file(s) as not processed (<processed>no</processed>). The receiver will have to copy the xml-files to Resources/patch and then restart his application. During the restart Sympatch will look for non processed patch files, process them (onKernelRequest trigger) and mark them as processed.
How can I help you explore Laravel packages today?