Merge pull request #1674 from forcedotcom/sc/W-17100389

NEW: @W-17100389@: Add in feedback url to help text and log

Author: stephen-carter-at-sf

messages/config-command.md

@@ -8,6 +8,8 @@ Code Analyzer gives you the ability to configure settings that modify Code Analy
 
 To apply a custom configuration with Code Analyzer, either keep your custom configuration settings in a `code-analyzer.yml` file located in the current folder from which you are executing commands, or specify the location of your custom configuration file to the Code Analyzer commands with the --config-file flag.
 
+We're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.
+
 # command.examples
 
 - Display the current state of the Code Analyzer configuration using the default behavior: display top level configuration, display the engine and rule override settings associated with all the rules that have a "Recommended" tag; and automatically apply any existing custom configuration settings found in a `code-analyzer.yml` or `code-analyzer.yaml` file in the current folder: 

messages/path-start-util.md

@@ -1,7 +1,7 @@
 # error.glob-method-conflict
 
-*DRAFT*: Path start point %s is invalid: When specifying a method with the #methodName syntax, glob patterns cannot be used.
+Path start point %s is invalid: You can't use glob patterns when specifying a method with the #methodName syntax.
 
 # error.negative-globs-unsupported
 
-*DRAFT*: Path start point %s is invalid: Negative globs are unsupported.
+Path start point %s is invalid: Negative globs are unsupported.

messages/rules-command.md

@@ -8,6 +8,8 @@ You can also view details about the rules, such as the engine it's associated wi
 
 Use this command to determine the exact set of rules to analyze your code. The `code-analyzer run` command has similar flags as this command, so once you've determined the flag values for this command that list the rules you want to run, you specify the same values to the `code-analyzer run` command.
 
+We're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.
+
 # command.examples
 
 - List rules using the default behavior: include rules from all engines that have a "Recommended" tag; display the rules using concise table format; and automatically apply rule or engine overrides if a "code-analyzer.yml" or "code-analyzer.yaml" file exists in the current folder:

messages/run-command.md

@@ -8,6 +8,8 @@ You can scan your codebase with the recommended rules. Or use flags to filter th
 
 If you want to preview the list of rules before you actually run them, use the `code-analyzer rules` command, which also has the "--rules-selector", "--workspace", and "--config-file" flags that together define the list of rules to be run.
 
+We're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.
+
 # command.examples
 
 - Analyze code using the default behavior: analyze the files in the current folder (default workspace) using the Recommended rules; display the output in the terminal with the concise table view; and automatically apply rule or engine overrides if a "code-analyzer.yml" or "code-analyzer.yaml" file exists in the current folder:

messages/shared.md

@@ -5,3 +5,7 @@ Developer Preview
 # warning.command-state
 
 This command is in %s.
+
+# log.give-us-feedback
+
+We're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at http://sfdc.co/CodeAnalyzerFeedback.

messages/workspace-util.md

@@ -1,3 +1,3 @@
 # error.negative-globs-unsupported
 
-*DRAFT*: Workspace path %s is invalid: Negative globs are unsupported.
+Workspace path %s is invalid: Negative globs are unsupported.

src/lib/listeners/LogEventListener.ts

@@ -1,6 +1,7 @@
 import {CodeAnalyzer, EngineLogEvent, EventType, LogEvent, LogLevel} from '@salesforce/code-analyzer-core';
 import {Display} from '../Display';
 import {LogWriter} from '../writers/LogWriter';
+import {BundleName, getMessage} from "../messages";
 
 export interface LogEventListener {
 	listen(codeAnalyzer: CodeAnalyzer): void;
@@ -58,6 +59,7 @@ export class LogEventLogger implements LogEventListener {
 	}
 
 	public stopListening(): void {
+		this.logWriter.writeToLog('\n' + getMessage(BundleName.Shared, 'log.give-us-feedback'));
 		this.logWriter.closeLog();
 	}