docs(no-pass-data-to-parent): elaborate on best way to handle passing refs TODOs

#22
#37

Author: NickvanDyke

src/no-pass-data-to-parent.js

@@ -46,8 +46,11 @@ export default {
                 (ref) =>
                   !isState(context, ref) &&
                   !isProp(context, ref) &&
-                  // TODO: Should warn to use `forwardRef` instead?
+                  // TODO: Should advise to use `forwardRef` instead?
+                  // Not always the best solution, but usually, and outliers can silence the warning.
+                  // Could possibly check for refs on the "path" to this callback too.
                   // https://github.com/NickvanDyke/eslint-plugin-react-you-might-not-need-an-effect/issues/22
+                  // https://github.com/NickvanDyke/eslint-plugin-react-you-might-not-need-an-effect/issues/37
                   !isRef(context, ref),
               )
           ) {

test/no-pass-data-to-parent.test.js

@@ -138,7 +138,6 @@ new MyRuleTester().run("no-pass-data-to-parent", rule, {
     {
       // https://github.com/NickvanDyke/eslint-plugin-react-you-might-not-need-an-effect/issues/37
       // Alternate solutions exist, but this is arguably the most readable.
-      // TODO: There is probably a more granular opportunity here...
       name: "Pass cleanup function that depends on ref",
       code: js`
         import { dropTargetForElements } from "@atlaskit/pragmatic-drag-and-drop/element/adapter";