Merge pull request #217 from sasjs/readme

fix: README update (to trigger release with new GH_TOKEN)

README.md

@@ -21,7 +21,6 @@ Configuration is via a `.sasjslint` file with the following structure (these are
 
 ```json
 {
-  "noEncodedPasswords": true,
   "hasDoxygenHeader": true,
   "hasMacroNameInMend": true,
   "hasMacroParentheses": true,
@@ -34,6 +33,7 @@ Configuration is via a `.sasjslint` file with the following structure (these are
   "maxDataLineLength": 80,
   "maxHeaderLineLength": 80,
   "maxLineLength": 80,
+  "noEncodedPasswords": true,
   "noNestedMacros": true,
   "noGremlins": true,
   "noSpacesInFileNames": true,
@@ -90,13 +90,6 @@ If creating a new value, use `{lineEnding}` instead of `\n`, eg as follows:
 }
 ```
 
-### noEncodedPasswords
-
-This rule will highlight any rows that contain a `{sas00X}` type password, or `{sasenc}`. These passwords (especially 001 and 002) are NOT secure, and should NEVER be pushed to source control or saved to the filesystem without special permissions applied.
-
-- Default: true
-- Severity: ERROR
-
 ### hasDoxygenHeader
 
 The SASjs framework recommends the use of Doxygen headers for describing all types of SAS program. This check will identify files where a doxygen header does not begin in the first line.
@@ -221,6 +214,13 @@ See also:
 - [maxDataLineLength](#maxdatalinelength)
 - [maxHeaderLineLength](#maxheaderlinelength)
 
+### noEncodedPasswords
+
+This rule will highlight any rows that contain a `{sas00X}` type password, or `{sasenc}`. These passwords (especially 001 and 002) are NOT secure, and should NEVER be pushed to source control or saved to the filesystem without special permissions applied.
+
+- Default: true
+- Severity: ERROR
+
 ### noGremlins
 
 Capture zero-width whitespace and other non-standard characters. The logic is borrowed from the [VSCode Gremlins Extension](https://github.com/nhoizey/vscode-gremlins) - if you are looking for more advanced gremlin zapping capabilities, we highly recommend to use their extension instead.