feat: support escaped expressions #11
Merged
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.
Proposed changes
Hatter uses
{{ }}for expression evaluation (e.g.,{{ faker.lastName() }}). However, some use cases require outputting literal{{ }}in fixture data - for example when fixtures contain template strings that use the same syntax for variable substitution at runtime.Currently, there is no way to output literal
{{ }}in a Hatter fixture. Any{{content}}is interpreted as an expression and evaluated.This PR adds support for backslash escaping:
\{{name}}outputs literal{{name}}without evaluation.Usage Example
Backward Compatibility
The backslash escape is new syntax that was previously invalid (would have caused an expression evaluation error), so no existing fixtures are affected.
Checklist
Further comments