Searched hist:"4 b31eadfd0dd82e519dd953a4cb0ad079114879d" (Results 1 – 4 of 4) sorted by relevance
| /dokuwiki/inc/Parsing/ParserMode/ |
| H A D | GfmHeader.php | 4b31eadfd0dd82e519dd953a4cb0ad079114879d Thu Jun 04 14:35:00 UTC 2026 Andreas Gohr <gohr@cosmocode.de> fix (parsing): avoid newline loss on GFM section editing
The GFM header parsing returned a byte position pointing at the newline
before the actual header resulting in the observed newline eatings as
reported in https://github.com/dokuwiki/dokuwiki/pull/4636#issuecomment-4491970909
Additionally this fixes an oddity of DW header parsing which
accidentally allowed text on the line before the opening = chars.
Whitespace is still allowed.
|
| H A D | Header.php | 4b31eadfd0dd82e519dd953a4cb0ad079114879d Thu Jun 04 14:35:00 UTC 2026 Andreas Gohr <gohr@cosmocode.de> fix (parsing): avoid newline loss on GFM section editing
The GFM header parsing returned a byte position pointing at the newline
before the actual header resulting in the observed newline eatings as
reported in https://github.com/dokuwiki/dokuwiki/pull/4636#issuecomment-4491970909
Additionally this fixes an oddity of DW header parsing which
accidentally allowed text on the line before the opening = chars.
Whitespace is still allowed.
|
| /dokuwiki/_test/tests/Parsing/ParserMode/ |
| H A D | HeadersTest.php | 4b31eadfd0dd82e519dd953a4cb0ad079114879d Thu Jun 04 14:35:00 UTC 2026 Andreas Gohr <gohr@cosmocode.de> fix (parsing): avoid newline loss on GFM section editing
The GFM header parsing returned a byte position pointing at the newline
before the actual header resulting in the observed newline eatings as
reported in https://github.com/dokuwiki/dokuwiki/pull/4636#issuecomment-4491970909
Additionally this fixes an oddity of DW header parsing which
accidentally allowed text on the line before the opening = chars.
Whitespace is still allowed.
|
| H A D | GfmHeaderTest.php | 4b31eadfd0dd82e519dd953a4cb0ad079114879d Thu Jun 04 14:35:00 UTC 2026 Andreas Gohr <gohr@cosmocode.de> fix (parsing): avoid newline loss on GFM section editing
The GFM header parsing returned a byte position pointing at the newline
before the actual header resulting in the observed newline eatings as
reported in https://github.com/dokuwiki/dokuwiki/pull/4636#issuecomment-4491970909
Additionally this fixes an oddity of DW header parsing which
accidentally allowed text on the line before the opening = chars.
Whitespace is still allowed.
|