Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
woocommerce/bin/prefix-vendor-namespaces.sh

30 lines
919 B
Bash
Raw Normal View History

Reintroduce the League's Container package, and prefix it. All the classes in the package are re-namespaced from "Leage\Container" to "Automattic\WooCommerce\Vendor\League\Container" to prevent conflicts with extensions using the same plugin. The re-namespacing is done by using a simple text substitution on all the code files (see prefix-vendor-namespaces.sh), for this particular case this approach is enough.
2020-09-21 14:20:18 +00:00
#!/bin/sh
De-refactor the output function in scripts
2020-10-06 07:36:18 +00:00
# Output colorized strings
#
# Color codes:
# 0 - black
# 1 - red
# 2 - green
# 3 - yellow
# 4 - blue
# 5 - magenta
# 6 - cian
# 7 - white
output() {
echo "$(tput setaf "$1")$2$(tput sgr0)"
}
Reintroduce the League's Container package, and prefix it. All the classes in the package are re-namespaced from "Leage\Container" to "Automattic\WooCommerce\Vendor\League\Container" to prevent conflicts with extensions using the same plugin. The re-namespacing is done by using a simple text substitution on all the code files (see prefix-vendor-namespaces.sh), for this particular case this approach is enough.
2020-09-21 14:20:18 +00:00
output 6 "Prefixing the appropriate vendor namespaces with Automattic\WooCommerce\Vendor"
Adjust the namespace prefixing script to macOS/Linux Both OSes have a slightly different syntax for "sed -i" and therefore two versions of the command are needed.
2020-09-22 07:19:12 +00:00
# Replace "League\Container" in "use" and "namespace" with "Automattic\WooCommerce\Vendor\League\Container".
REGEX='s/^[[:space:]]*(use|namespace)[[:space:]]*(League\\Container)/\1 Automattic\\WooCommerce\\Vendor\\\2/g'
Fix error in the sed commands used to prefix namespaces This commit fixes a minor error in the sed commands used to prefix namespaces in the vendor folder. Due to an extra space sed was considering `.bak` an extra parameter. If we use `-i.bak` instead (without the space), sed creates a backup file which is the desired behavior. With this change we won't be getting the errors below when running `composer install` or `composer update`: ``` Generating autoload files > sh ./bin/prefix-vendor-namespaces.sh Prefixing the appropriate vendor namespaces with Automattic\WooCommerce\Vendor sed: can't read .bak: No such file or directory sed: can't read .bak: No such file or directory sed: can't read .bak: No such file or directory (...) ``` Since sed was working without creating a backup file, I wonder if we really need to create one. I tested and `sed -i -E -e "s/\"(League\\\\\\\Container)/\"Automattic\\\\\\\WooCommerce\\\\\\\Vendor\\\\\\\\\1/g" vendor/league/container/composer.json` works well in Linux. If it also works on Mac, maybe we can use it and remove the code that deletes the .bak files?
2020-10-21 12:26:30 +00:00
find ./vendor/league/container -iname '*.php' -exec sed -i'.bak' -E -e "$REGEX" {} \;
Improvements on prefix-vendor-namespaces.sh - Prefix also Container's composer.json - Use one single variant for sed, creating a backup file and later deleting it
2020-09-25 09:15:12 +00:00
find ./vendor/league/container -name "*.php.bak" -type f -delete
# Replace too in the composer.json file for the package.
Fix error in the sed commands used to prefix namespaces This commit fixes a minor error in the sed commands used to prefix namespaces in the vendor folder. Due to an extra space sed was considering `.bak` an extra parameter. If we use `-i.bak` instead (without the space), sed creates a backup file which is the desired behavior. With this change we won't be getting the errors below when running `composer install` or `composer update`: ``` Generating autoload files > sh ./bin/prefix-vendor-namespaces.sh Prefixing the appropriate vendor namespaces with Automattic\WooCommerce\Vendor sed: can't read .bak: No such file or directory sed: can't read .bak: No such file or directory sed: can't read .bak: No such file or directory (...) ``` Since sed was working without creating a backup file, I wonder if we really need to create one. I tested and `sed -i -E -e "s/\"(League\\\\\\\Container)/\"Automattic\\\\\\\WooCommerce\\\\\\\Vendor\\\\\\\\\1/g" vendor/league/container/composer.json` works well in Linux. If it also works on Mac, maybe we can use it and remove the code that deletes the .bak files?
2020-10-21 12:26:30 +00:00
sed -i'.bak' -E -e "s/\"(League\\\\\\\Container)/\"Automattic\\\\\\\WooCommerce\\\\\\\Vendor\\\\\\\\\1/g" vendor/league/container/composer.json
Improvements on prefix-vendor-namespaces.sh - Prefix also Container's composer.json - Use one single variant for sed, creating a backup file and later deleting it
2020-09-25 09:15:12 +00:00
rm -f vendor/league/container/composer.json.bak