Skip to content

Instantly share code, notes, and snippets.

@roguh
Last active February 3, 2019 18:21
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save roguh/7289673c7291c912ae15b54d4ed3ce59 to your computer and use it in GitHub Desktop.
Save roguh/7289673c7291c912ae15b54d4ed3ce59 to your computer and use it in GitHub Desktop.
#!/bin/sh
STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep -v "node_modules" | grep -E '\.(js|jsx)$')
if [[ "$STAGED_FILES" = "" ]]; then
exit 0
fi
PASS=true
printf '%b\n' "\nValidating Javascript:\n"
# Check for eslint
ESLINT="$(git rev-parse --show-toplevel)/node_modules/.bin/eslint"
if [[ ! -x "$ESLINT" ]]; then
printf '%b\n' "\t\033[41mPlease install ESlint\033[0m (npm i --save --save-exact --dev eslint)"
exit 1
fi
for FILE in $STAGED_FILES
do
if test -e "$FILE"; then
"$ESLINT" "$FILE"
if [[ "$?" == 0 ]]; then
printf '%b\n' "\t\033[32mESLint Passed: $FILE\033[0m"
else
printf '%b\n' "\t\033[41mESLint Failed: $FILE\033[0m"
PASS=false
fi
fi
done
printf '%b\n' "\nJavascript validation completed!\n"
if ! $PASS; then
printf '%b\n' "\033[41mCOMMIT FAILED:\033[0m Your commit contains files that should pass ESLint but do not. Please fix the ESLint errors and try again.\n"
exit 1
else
printf '%b\n' "\033[42mCOMMIT SUCCEEDED\033[0m\n"
fi
exit $?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment