style: wrap long lines

Author: MichaelCurrin

.vscode/settings.json

@@ -5,11 +5,15 @@
   "search.exclude": {
     "out": true
   },
-  // Turn off tsc task auto detection since we have the necessary tasks as npm scripts.
+  // Turn off tsc task auto detection since we have the necessary tasks as npm
+  // scripts.
   "typescript.tsc.autoDetect": "off",
 
   // For Prettier Now extension. I don't like how this has to be set
-  // vs the the TS JS language features extension. Plus Prettier Now wraps else statements weirdly. Oh but Prettier Now removes empty lines for cleanup and the other doesn't. So I don't know which to use. Maybe prettier is better as it is meant to avoid discussions like this.
+  // vs the the TS JS language features extension. Plus Prettier Now wraps else
+  // statements weirdly. Oh but Prettier Now removes empty lines for cleanup and
+  // the other doesn't. So I don't know which to use. Maybe prettier is better
+  // as it is meant to avoid discussions like this.
   "prettier.tabWidth": 2,
 
   "grammarly.autoActivate": true,

bin/reset_sandbox.sh

@@ -11,7 +11,8 @@ fi
 git init "$DIR" --quiet
 cd "$DIR"
 
-# Create a commit, so that the extension can run diff-index, which requires an initial commit.
+# Create a commit, so that the extension can run diff-index, which requires an
+# initial commit.
 echo "# Sandbox\n" >'README.md'
 echo 'console.log("Hello, Foo!");' >foo.js
 echo 'console.log("Hello, Fizz!");' >fizz.js

shell/autofill-hook.sh

@@ -1,14 +1,15 @@
 #!/usr/bin/env bash
 # CLI test.
 #
-# This script is *not* ready to be used in other projects. See shell/README.md for dev notes.
+# This script is *not* ready to be used in other projects. See shell/README.md
+# for dev notes.
 #
-# This is a pure CLI that script bypasses using VS Code or an extension. It will get output from
-# git, send it to Node CLI entry-point tool and print it. This can be used as part of git commit
-# message hook flow.
+# This is a pure CLI that script bypasses using VS Code or an extension. It will
+# get output from git, send it to Node CLI entry-point tool and print it. This
+# can be used as part of git commit message hook flow.
 #
-# Optionally add a `-d` debug flag to print without writing to a file. This makes it easy to debug
-# the script outside a git commit hook flow.
+# Optionally add a `-d` debug flag to print without writing to a file. This
+# makes it easy to debug the script outside a git commit hook flow.
 #  ./autofill-hook.sh -p
 #
 # See shell/README.md doc.

shell/autofill.sh

@@ -3,7 +3,8 @@
 #
 # Produce a commit message from changed files and print to stdout.
 
-# This works similar to a Git hook, but is intended to be used alone or in a Git alias.
+# This works similar to a Git hook, but is intended to be used alone or in a Git
+# alias.
 #
 # See shell/README.md doc.
 # See src/git/cli.ts for flags.

shell/count-files.sh

@@ -1,20 +1,23 @@
 #!/usr/bin/env bash
-# Proof of concept script to use Bash to produce report of file counts from git status.
+# Proof of concept script to use Bash to produce report of file counts from git
+# status.
 #
-# Run this as a standalone report, not as a hook. If you use this as a hook, it will
-# print output in the console only not add to commit message
+# Run this as a standalone report, not as a hook. If you use this as a hook, it
+# will print output in the console only not add to commit message
 #
 # See simple-hook.sh script for how CHANGES
 # would get written out to a commit message file.
 #
-# This script will get count of files added, modified, deleted and renamed/moved and output it.
-# Note that modified and renamed/moved can both apply to the same file.
+# This script will get count of files added, modified, deleted and renamed/moved
+# and output it. Note that modified and renamed/moved can both apply to the same
+# file.
 # This does not support C (copied).
 
 # This report uses git status and passes it do the steps below to parse it.
 # A more flexible approach (for unit tests for example) would be for this
-# script to handle the status and call another script to do the parsing and result. Then
-# the script could be used separate from git and so accept a filename or stdin.
+# script to handle the status and call another script to do the parsing and
+# result. Then the script could be used separate from git and so accept a
+# filename or stdin.
 
 # Status summary excluding untracked files using a flag.
 CHANGES=$(git status -s -uno --porcelain)

shell/sample.sh

@@ -1,7 +1,10 @@
 #!/bin/sh
 
-# This script is based on the prepare-commit-msg.sample file that comes by default in any git repo when you run git init or git clone (you can also run git init later on to restore hooks).
-# Note everything here is uncommented but you're only meant to run one of the 3 sections after setting up vars.
+# This script is based on the prepare-commit-msg.sample file that comes by
+# default in any git repo when you run git init or git clone (you can also run
+# git init later on to restore hooks).
+# Note everything here is uncommented but you're only meant to run one of the 3
+# sections after setting up vars.
 
 # e.g. '.git/COMMIT_EDITMSG'
 COMMIT_MSG_FILE=$1
@@ -13,13 +16,15 @@ SHA1=$3
 ###
 
 # Remove line.
-/usr/bin/perl -i.bak -ne 'print unless(m/^. Please enter the commit message/..m/^#$/)' "$COMMIT_MSG_FILE"
+/usr/bin/perl -i.bak \
+  -ne 'print unless(m/^. Please enter the commit message/..m/^#$/)' \
+  "$COMMIT_MSG_FILE"
 
 ###
 
 # Show files change.
-# (It will uncomment files changed in the message - which is maybe less efficient than just running git status but this is what git comes with.)
-#
+# (It will uncomment files changed in the message - which is maybe less
+# efficient than just running git status but this is what git comes with.)
 case "$COMMIT_SOURCE,$SHA1" in
 , | template,)
   /usr/bin/perl -i.bak -pe '

shell/simple-hook.sh

@@ -3,13 +3,16 @@
 #
 # Usage:
 #   ./simple-hook.sh MSG SRC SHA [-d]
-# The last part is an optional non-standard flag, allowing this to be run directly without writing out.
+# The last part is an optional non-standard flag, allowing this to be run
+# directly without writing out.
 #
-# This uses a call to `git status`, processes the text, writes out to a commit message file.
+# This uses a call to `git status`, processes the text, writes out to a commit
+# message file.
 
 set -e
 
-# These are the 3 standard prepare-commit-msg args as per the hooks example and git hook docs.
+# These are the 3 standard prepare-commit-msg args as per the hooks example and
+# git hook docs.
 COMMIT_MSG_FILE=$1
 COMMIT_SOURCE=$2
 SHA1=$3

src/cli.ts

@@ -1,13 +1,14 @@
 /**
  * CLI module.
  *
- * This is the entry-point for the Auto Commit Message tool when running as a STANDALONE
- * command-line script i.e. without VS Code.
+ * This is the entry-point for the Auto Commit Message tool when running as a
+ * STANDALONE command-line script i.e. without VS Code.
  *
  * This script does NOT interact with VS Code or the Git.
  *
- * It simply receives text as an argument and prints output to `stdout` for use in a hook flow. Or
- * `stderr`, in the case of a message not appropriate for a commit message.
+ * It simply receives text as an argument and prints output to `stdout` for use
+ * in a hook flow. Or `stderr`, in the case of a message not appropriate for a
+ * commit message.
  *
  * See `shell/README.md` in docs.
  */

src/generate/convCommit.ts

@@ -37,8 +37,8 @@ export class ConventionalCommit {
     // TODO It is worth keeping splitPath on its own for separation of concerns,
     // but could it work better as a class? And then conv commit can inherit
     // from it.
-    // The properties are actually all the same her as there (duplication), only the conv commit
-    // methods get added here as new.
+    // The properties are actually all the same her as there (duplication), only
+    // the conv commit methods get added here as new.
     //
     // Maybe a class is overkill as it is just a container of data.
     // Maybe the {} can be stored an object here. Or maybe combine that and this

src/generate/count.ts

@@ -1,8 +1,8 @@
 /**
  * Count module.
  *
- * Rather than dealing with individual file names, this module deals with grouping files by actions
- * and showing a count for each.
+ * Rather than dealing with individual file names, this module deals with
+ * grouping files by actions and showing a count for each.
  *
  * e.g. 'create 5 files' (in different directories).
  * e.g. 'update 3 files in foo' (highest common directory).
@@ -54,7 +54,8 @@ export function _pluralS(count: number) {
 /**
  * Return a human-readable message a single action and count value.
  *
- * Anything works for action - it is not enforced to be one of ACTION or the MoveOrRename type.
+ * Anything works for action - it is not enforced to be one of ACTION or the
+ * MoveOrRename type.
  */
 export function _formatOne(action: string, count: number) {
   return `${action} ${count} file${_pluralS(count)}`;