Potential fix for code scanning alert no. 55: Assignment to constant

[vanshaj2023]

Potential fix for https://github.com/vectorMindsAI/vectorMindsAI-v0/security/code-scanning/55

In general, to fix “assignment to constant” issues, you either (1) stop reassigning the constant and rely on the original value, or (2) change the declaration from const to a reassignable binding such as let—but only if the design truly requires mutation. Here, the currentData value is read once from req.json() and used to construct enrichedData; there is no need to re-read or reassign it. The second destructuring on line 10 is redundant and invalid as written (missing const/let/var and trying to reassign a const).

The best minimal fix that preserves existing behavior is to remove the duplicate const { currentData } = await req.json() line entirely and keep the original destructuring const { city, currentData } = await req.json(). This way, currentData is read once, remains a constant, and is then used later when building enrichedData. No imports, additional methods, or other definitions are needed; only the single spurious assignment line should be deleted in app/api/enrich/route.ts.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.