fix(require-returns): don't report with forceRequireReturn when tag is explicitly undefined/void

If there is a force require return setting, we only want to reject on a lack of a returns tag, not
a function with an explicit `@returns {undefined}`

Author: brettz9

src/rules/requireReturns.js

@@ -64,9 +64,10 @@ export default iterateJsdoc(({
   }
 
   // In case the code returns something, we expect a return value in JSDoc.
-  if (!utils.hasDefinedTypeReturnTag(tags[0]) && (
-    utils.isForceRequireReturn() || utils.hasReturnValue()
-  )) {
+  const [tag] = tags;
+  if (!utils.hasDefinedTypeReturnTag(tag) && utils.hasReturnValue() ||
+    (typeof tag === 'undefined' || tag === null) && utils.isForceRequireReturn()
+  ) {
     report('Missing JSDoc @' + tagName + ' declaration.');
   }
 }, {

test/rules/assertions/requireReturns.js

@@ -408,6 +408,20 @@ export default {
         }
       }
       `
+    },
+    {
+      code: `
+          /**
+           * @returns {void}
+           */
+          function quux () {
+          }
+      `,
+      settings: {
+        jsdoc: {
+          forceRequireReturn: true
+        }
+      }
     }
   ]
 };