feat: add support for custom patch delimiters in PatchDocumentOptions #3036
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.
Resolves: #2972
What does this PR do?
Adds support for customizable placeholder delimiters in the
patchDocument
function.This allows users to define delimiters other than
{{ }}
, such as<< >>
,{ }
, or any custom format.Why is this needed?
Currently, the placeholder syntax is hardcoded to use
{{ }}
. This enhancement enables more flexibility when using different template styles or avoiding syntax collisions.How does it work?
placeholderDelimiters
field toPatchDocumentOptions
.{{
and}}
if none provided.patchText
is built.readonly
as per lint rules.Screenshots / Test Evidence
✅ Added tests for:
{{}}
Checklist
npm run lint
npm run test
Let me know if you'd like any changes!