fix: replace mutable let export with const getter function

[sonarqube-agent]

Resolved SonarQube critical issue by converting exported mutable 'let' binding to a module-private variable with an exported getter function. This prevents external code from directly reassigning the binding while maintaining read access, improving code safety and reducing the surface area for unintended mutations.

View Project in SonarCloud

---

Fixed Issues

typescript:S6861 - Exporting mutable 'let' binding, use 'const' instead. • CRITICAL • View issue

Location: data/datacache.ts:33

Why is this an issue?

In JavaScript, a mutable variable is one whose value can be changed after it has been initially set. This is in contrast to immutable variables, whose values cannot be changed once they are set.

What changed

This hunk directly fixes the issue of exporting a mutable 'let' binding for 'retrieveBlueprintChallengeFile'. Instead of using 'export let', the variable is renamed to '_retrieveBlueprintChallengeFile' and kept as a module-private 'let' (no longer exported). Access is provided through an exported getter function 'getRetrieveBlueprintChallengeFile()', which avoids exporting a mutable binding. External modules can read the value via the function but cannot directly reassign the variable, eliminating the code smell.

--- a/data/datacache.ts
+++ b/data/datacache.ts
@@ -33,1 +33,4 @@ export const notifications: Notification[] = []
-export let retrieveBlueprintChallengeFile: string | null = null
+let _retrieveBlueprintChallengeFile: string | null = null
+export function getRetrieveBlueprintChallengeFile (): string | null {
+  return _retrieveBlueprintChallengeFile
+}

Have a suggestion or found an issue? Share your feedback here.

---

SonarQube Remediation Agent uses AI. Check for mistakes.