fix(ci): anchor AST goldens to LF bytes and test CRLF explicitly
The Windows CI failure was a checkout byte-identity problem, not a Markdown semantics change: CRLF goldens compared with LF parser output produced '0 line(s) differ'. - add .gitattributes: text files are LF, native products are binary, and the intentional CRLF fixture stays a byte fixture - report the first differing byte and whether only line endings differ - fail early when a golden contains CR instead of the opaque mismatch - assert exactly one CRLF fixture and that its golden is canonical LF - add a markdown test proving CRLF/LF have equal structure while spans remain byte offsets into the original source
This commit is contained in:
1 parent
e966b7661f
commit
c7f3a8422c
4 files changed
+244
-3
No files matched your search
@@ -0,0 +1,20 @@
|
||||
# Canonical byte identity for the repository.
|
||||
#
|
||||
# The frozen Markdown profile and its AST goldens are compared byte-for-byte.
|
||||
# Normalize every text file to LF on checkout so a Windows clone does not turn
|
||||
# golden JSON into CRLF (which previously produced a confusing "0 line(s)
|
||||
# differ" failure). Line-ending semantics are tested explicitly with the
|
||||
# dedicated CRLF fixture below instead of relying on the checkout platform.
|
||||
* text=auto eol=lf
|
||||
|
||||
# Intentional byte-level CRLF fixture (see spec/markdown-profile.md §3).
|
||||
# It must keep its original CRLF bytes on every platform.
|
||||
tests/conformance/ast/146-crlf-line-endings.mq.md -text -eol
|
||||
|
||||
# Native build products are not text.
|
||||
*.so binary
|
||||
*.dylib binary
|
||||
*.dll binary
|
||||
*.a binary
|
||||
*.lib binary
|
||||
*.exe binary
|
||||
Reference in new issue
Block a user