GHAS. Translations. Fix Incomplete string escaping or encoding #19375
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes https://github.com/SAP/spartacus/security/code-scanning/55
To fix the problem, we need to ensure that backslashes are properly escaped in the
stringify
function. This can be done by adding a step to replace backslashes with double backslashes before handling other characters. Specifically, we should update thereplace
method on line 151 to first escape backslashes and then handle double quotes.stringify
function to include backslash escaping.replace
method to handle backslashes before replacing double quotes.scripts/i18n/convert-translations-json-2-ts.ts
file.Suggested fixes powered by Copilot Autofix. Review carefully before merging.