Files
odoo_source/addons/web/tooling/disable.sh
T
Simon Genin (ges) f5c5e51917 [FIX] web: tooling: fix support for older tooling
Older tooling used prettier config files. The issue was that the
disable command of the tooling was also changed to not remove those
files as they shouldn't exist anymore.
But changing from 16 to master without manually triggering a tooling
"disable" would then left the prettier config and mess with the addons
eslint whitelist.

closes odoo/odoo#110582

Signed-off-by: Samuel Degueldre <sad@odoo.com>
2023-01-26 14:19:06 +01:00

40 lines
997 B
Bash
Executable File

#!/bin/bash
community=$(cd -- "$(dirname "$0")" &> /dev/null && cd ../../.. && pwd)
disableInDir () {
cd "$1" || exit
git config --unset core.hooksPath
rm .eslintignore
rm .eslintrc.json
rm jsconfig.json
rm package.json
rm package-lock.json
rm -r node_modules
# to support old versions
rm -f .prettierignore
rm -r .prettierrc.json
cd - &> /dev/null
}
read -p "Do you want to delete the tooling installed in enterprise too ? [y, n]" willingToDeleteToolingInEnterprise
if [[ $willingToDeleteToolingInEnterprise != "n" ]]
then
read -p "What is the relative path from community to enterprise ? (../enterprise)" pathToEnterprise
pathToEnterprise=${pathToEnterprise:-../enterprise}
pathToEnterprise=$(realpath "$community/$pathToEnterprise")
fi
disableInDir "$community"
if [[ $willingToDeleteToolingInEnterprise != "n" ]]
then
disableInDir "$pathToEnterprise"
fi
echo ""
echo "JS tooling have been removed from the roots"
echo ""