Fix for code scanning alert no. 27: Clear-text logging of sensitive i…

…nformation (#8301)

* Potential fix for code scanning alert no. 27: Clear-text logging of sensitive information

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

* Changeset

---------

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

.changeset/tiny-fans-drive.md

@@ -0,0 +1,8 @@
+---
+'@graphql-mesh/string-interpolation': patch
+---
+
+Avoid logging sensitive data directly. Instead, log a generic error message without including the potentially sensitive str variable. This way, it still notifies of errors without risking the exposure of sensitive information.
+
+- Replace the logging statement on line 176 in `packages/string-interpolation/src/interpolator.js` to avoid logging the `str` variable.
+- Ensure that the new logging statement provides enough information to debug the issue without exposing sensitive data.

packages/string-interpolation/src/interpolator.js

@@ -173,7 +173,7 @@ export class Interpolator {
         str,
       );
     } catch (e) {
-      console.error(`An error occurred while applying modifiers to ${str}`, modifiers, e);
+      console.error(`An error occurred while applying modifiers`, e);
       return str;
     }
   }