Skip to content

Commit a2b8853

Browse files
authored
Fix error_location spec substrings to match common error messages (#157)
- parse_error_line_3_structured: 'if' → 'not properly terminated' (the tag name may not appear in all implementations' error messages) - partial_error_line_2_structured: 'bad_syntax' → 'not properly terminated' (the partial name may not appear in raised exceptions, only in inline output)
1 parent 911a180 commit a2b8853

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

specs/basics/error-handling.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -466,7 +466,7 @@
466466
{% if true
467467
errors:
468468
parse_error:
469-
- "if"
469+
- "not properly terminated"
470470
line: 3
471471
complexity: 530
472472
error_mode: lax
@@ -538,12 +538,12 @@
538538
{% if true
539539
errors:
540540
render_error:
541-
- "bad_syntax"
541+
- "not properly terminated"
542542
line: 2
543543
complexity: 540
544544
error_mode: lax
545545
hint: |
546546
A parse error on line 2 of a rendered partial. The structured
547547
'line: 2' key checks the exception's line attribute (relative to
548-
the partial source). The 'bad_syntax' substring verifies the
548+
the partial source). The substring verifies the
549549
partial name is in the error.

0 commit comments

Comments
 (0)