fix: keyword replacement handling for special characters #1174
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.
🔧 Changes
Fixed keyword replacement handling for special
$sequences, which was causing corruption of keyword values containing these sequences (issue #1153).Impact: Keyword replacement now correctly values containing special
$sequences, eliminating silent data corruption during multi-environment deployments.📚 References
• Fixes #1153
🔬 Testing
• New test cases added:
should handle dollar-apostrophe in replacement value— Validates string replacement preserves$'sequencesshould handle dollar-apostrophe in array values— Validates array replacement preserves$'sequences in multiple array elements📝 Checklist