v2.0.2
A one-fix patch release: an unterminated ${ placeholder in a seed fixture is now rejected instead of being seeded as literal text.
Highlights
- 01
A placeholder typo fails the test, not the data
A seed fixture containing
Read the guide →"note": "${orderId"uses a${with no closing brace. It used to pass straight through the rewriter and seed the literal string${orderId. The typo became test data silently: the assertion that depended on it failed somewhere unrelated, or passed for the wrong reason. The rewriter now raisesPlaceholderExceptionnaming the fixture, the JSON path and the offending text, and points at the$${...}escape for a genuinely literal${...}. Escaped placeholders and ordinary$text behave exactly as before.
Full notes
Fixed
- The seed placeholder rewriter rejects an unterminated
${with aPlaceholderExceptionnaming the source, JSON path and offending text, instead of emitting it as a literal string. Found while porting the same engine to a sibling project, and fixed identically in both.