| Age | Commit message (Collapse) | Author |
|
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.
|
|
Using struct limit the value to only string, while some attributes
can be an integer value, for example "leveloffset".
|
|
|
|
The inline passthrough "pass:" can be used to control the substitutions
applied to a run of text.
Ref: https://docs.asciidoctor.org/asciidoc/latest/pass/pass-macro/
|
|
Macro footnote grammar,
----
"footnote:" [ REF_ID ] "[" STRING "]"
----
In asciidoctor, footnote can be placed anywhere, even after WORD without
space in between.
The REF_ID, define the unique ID for footnote and can be used to reference
the previous footnote.
The first footnote with REF_ID, should have the STRING defined.
The next footnote with the same REF_ID, should not have the STRING
defined; if its defined, the STRING is ignored.
|
|
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.
|
|
Use raw string literal whenever possible.
|
|
Replace any usage of ":=" with "var" declaration with type.
The ideas is to make the code reader know what is the expected return
value of function/method.
|
|
Signed-off-by: Shulhan <ms@kilabit.info>
|
|
The latest update on share v0.25.1 remove the last boolean parameter
on lib/test.Assert().
|
|
This is to minimize call stack size since the method will be called
recursively.
|
|
Instead of parserX (or parser_x.go) we move the X as prefix so it will
become XParser (or x_parser.go).
|