fix(newline-afer-description): correctly treat carriage return immediately after newline as ending with a newline; fixes #437

Since `comment-parser` cuts off at newlines, we can get stuck with a carriage return at end when in a non-trimming rule; handle this.

Author: brettz9

README.md

@@ -4454,6 +4454,19 @@ function quux () {
 
 }
 // Options: ["always"]
+
+/**
+ * Parses query string to object containing URL parameters
+ * 
+ * @param queryString
+ * Input string
+ * 
+ * @returns
+ * Object containing URL parameters
+ */
+export function parseQueryString(queryString: string): { [key: string]: string } {    // <-- Line 10 that fails
+
+}
 ````
 
 

src/rules/newlineAfterDescription.js

@@ -21,7 +21,7 @@ export default iterateJsdoc(({
     always = true;
   }
 
-  const descriptionEndsWithANewline = jsdoc.description.endsWith('\n');
+  const descriptionEndsWithANewline = (/\n\r?$/).test(jsdoc.description);
 
   if (always) {
     if (!descriptionEndsWithANewline) {

test/rules/assertions/newlineAfterDescription.js

@@ -299,5 +299,26 @@ export default {
         'always',
       ],
     },
+    {
+      // https://github.com/gajus/eslint-plugin-jsdoc/issues/437
+      code: `
+      /**\r
+       * Parses query string to object containing URL parameters\r
+       * \r
+       * @param queryString\r
+       * Input string\r
+       * \r
+       * @returns\r
+       * Object containing URL parameters\r
+       */\r
+      export function parseQueryString(queryString: string): { [key: string]: string } {    // <-- Line 10 that fails\r
+\r
+      }\r
+      `,
+      parser: require.resolve('@typescript-eslint/parser'),
+      parserOptions: {
+        sourceType: 'module',
+      },
+    },
   ],
 };