asciidoctor-go/testdata/inline_parser/inline_parser_test.txt, branch mainNative Go parser for asciidoc markup.http://git.kilabit.info/asciidoctor-go/atom?h=main2026-02-18T04:12:44Zall: fix parsing inline format with escaped character2026-02-18T04:12:44ZShulhanms@kilabit.info2026-02-18T04:12:44Zurn:sha1:974b8b5068b688258dbe1ffcc37d0ce0f3f4b4c7
If the text inside the inline format contains escaped character, the
parsing failed to find the closed character which cause the format is
not rendered as expected.
all: rewrite unit tests for inlineParser using test.Data2022-08-05T18:17:10ZShulhanms@kilabit.info2022-08-05T18:16:08Zurn:sha1:9fe1ecf6050bbebfe4096e5c41a1e711dd16190d
Using string literal for testing string input that may contains backtick
or double quote make the test code become unreadable and hard to modify.
The test.Data help this by moving the input and expected output into
a file that can we write as is.