update code comments with more context

Author: abdulahmad307

.github/actions/find/src/dynamicImport.ts

@@ -1,9 +1,21 @@
 // - this exists because I'm not sure how to mock
 //   the dynamic import function, so mocking this instead
+//   (also, if it _is_ possible to mock the dynamic import,
+//   there's the risk of altering/breaking the behavior of imports
+//   across the board - including non-dynamic imports)
+//
 // - also, vitest has a limitation on mocking:
 //   https://vitest.dev/guide/mocking/modules.html#mocking-modules-pitfalls
+//
 // - basically if a function is called by another function in the same file
 //   it can't be mocked. So this was extracted into a separate file
+//
+// - one thing to note is vitest does the same thing here:
+//   https://github.com/vitest-dev/vitest/blob/main/test/core/src/dynamic-import.ts
+// - and uses that with tests here:
+//   https://github.com/vitest-dev/vitest/blob/main/test/core/test/mock-internals.test.ts#L27
+//
+// - so this looks like a reasonable approach
 export async function dynamicImport(path: string) {
   return import(path)
 }

.github/actions/find/src/findForUrl.ts

@@ -35,8 +35,10 @@ export async function findForUrl(
       rawFindings = await new AxeBuilder({page}).analyze()
     }
 
-    // - this condition is not required, but makes it easier to make assertions
-    //   in unit tests on whether 'loadPlugins' was called or not
+    // - this if condition is not required, but makes it easier to make assertions
+    //   in unit tests on whether 'loadPlugins' was called or not (it does have the added
+    //   benefit of completely skipping plugin loading if we just want axe - so thats
+    //   a minor performance boost)
     // - alternatively, we can wrap the 'plugin.default(...)' call in another function
     //   and make assertions on whether that function was called or not
     // - the other option is to wrap each plugin in a class instance