Changes in Parser.php

21d6f17628c4d23bbd68d3bc6875455198d9fbe6 - fix(parser): restore BC for manual Handler/Parser construction

Sun, 05 Jul 2026 16:28:58 +0000

fix(parser): restore BC for manual Handler/Parser constructionThe parser rework made ModeRegistry a required constructor argument onHandler and Parser and dropped the Doku_Parser class alias, breaking thelong-documented manual sub-parsing pattern used by many plugins(new Doku_Handler(); new Parser($handler); ...): both threwArgumentCountError and new Doku_Parser() fatalled as an unknown class.Default the ModeRegistry argument on both constructors: Handler builds aregistry for the configured syntax, Parser takes it from the handler.Re-add the Doku_Parser alias. Constructing without a registry emits adeprecation pointing at p_get_instructions(). List of files: /dokuwiki/inc/Parsing/Parser.php

47a02a102092be9e1e6f1ddaf158bdfffdb13d4f - Parsing: make parse syntax a per-parse value, drop ModeInterface

Thu, 04 Jun 2026 12:27:59 +0000

Parsing: make parse syntax a per-parse value, drop ModeInterfaceThe active parse's syntax flavour is a per-parse question, not process-global state: within a single request a plugin can render bundledDokuWiki-syntax text inside an otherwise-Markdown page. Yet ModeRegistrywas a singleton that read $conf['syntax'] and the $PARSER_MODES global,and every mode reached it through ModeRegistry::getInstance() — so theflavour lived in shared mutable state that two parses in one requestwould fight over.Make the registry a short-lived value instead:- ModeRegistry is constructed once per parse with an explicit $syntax and injected into Parser, Handler and every mode. getSyntax() / isDwPreferred() / isMdPreferred() consult $this->syntax; the DOKU_UNITTEST-gated mode-list cache hack is gone (each registry is fresh, nothing to invalidate).- p_get_instructions() is now the single place in the pipeline where $conf['syntax'] is read; from there the flavour travels as a parameter. No code under inc/Parsing/ reads $conf['syntax'] directly anymore — the five syntax-reading modes (Preformatted, GfmHr, GfmEscape, Externallink, GfmQuote) route through $this->registry.Keep the two concepts apart, as documented in the ModeRegistry andAbstractMode docblocks: the user's configured *preference* stays in$conf['syntax'] for UI code (toolbar, settings), while the activeparse's syntax is a parameter carried by the registry.$PARSER_MODES is demoted to a deprecated, read-only mirror, publishedduring loadPluginModes() — third-party syntax plugins (columnlist,alphalist2, phpwikify, skipentity) and the bundled info plugin read theglobal directly, often from their constructors, so the taxonomy muststay visible there. No core code reads the mirror.Fold ModeInterface into AbstractMode while here: getSort()/handle() areabstract, the connect callbacks carry defaults, and the public $Lexer"FIXME should be done by setter" becomes setLexer()/getLexer() injectedby Parser::addMode() alongside the registry. Nested-content resolutionmoves to the allowedCategories()/filterAllowedModes() hooks, resolvedonce when the registry is attached.Tests build their own parser/registry through ParserTestBase::setSyntax()instead of mutating $conf and calling the removed ModeRegistry::reset(). List of files: /dokuwiki/inc/Parsing/Parser.php

9172eccff11a70df61d7aad697f84bbd815147ce - add sub-parser support to Handler / Parser / ModeRegistry

Tue, 28 Apr 2026 06:22:27 +0000

add sub-parser support to Handler / Parser / ModeRegistryA block mode that wants to parse the body of one of its capturedmatches needs a second Parser instance configured with the activemodes minus whatever would re-enter the outer mode. Doing this byhand is verbose and easy to get wrong — modes hold a $Lexer slotthat addMode() overwrites, so the same mode object can't be sharedbetween the main parser and a sub-parser.Three small additions: Handler::reset() — clears calls, status, currentModeName, and installs a fresh CallWriter. Lets one Handler instance be parsed against repeatedly without state bleed. Parser::getHandler() — accessor; sub-parser callers need it to reach the handler for reset() and for harvesting the produced call list. ModeRegistry::getSubParser($excludeCategories, $excludeModes) — returns a cached Parser preconfigured with every active mode except those excluded. Mode objects are cloned before being attached so connectTo()'s assignment to $Lexer does not clobber the main parser's references. Cache key is the exclusion-set; default exclusion is CATEGORY_BASEONLY (no Header inside the sub-parsed content).Tests cover Handler::reset's full clear, sub-parser caching,default and custom exclusions, registry-reset propagation, andthe clone-not-share invariant for $Lexer. List of files: /dokuwiki/inc/Parsing/Parser.php

71096e46fcbfaeaa808667aba794e77fe2780169 - move handler methods into ParserMode classes and rename Handler

Sat, 18 Apr 2026 15:35:30 +0000

move handler methods into ParserMode classes and rename HandlerEach ParserMode class now implements handle() from ModeInterface,containing the token handling logic that previously lived as individualmethods on Doku_Handler.The Handler class (formerly Doku_Handler) is the single dispatch point:Lexer passes tokens to Handler::handleToken() which routes to modeobjects, plugins, or returns false. The Lexer only tokenizes andresolves mapHandler aliases.Key changes:- Add handle() to ModeInterface, implemented by all mode classes- Move Doku_Handler to dokuwiki\Parsing\Handler namespace- File extends Code (shared parsing via $type property)- Quotes uses mapHandler() + Handler::getModeName() for sub-modes- Media::parseMedia() replaces Doku_Handler_Parse_Media()- Code::parseHighlightOptions() replaces parse_highlight_options()- Per-parse state (footnote, doublequote) stays on Handler- Deprecated wrappers kept for base/header/internallink/media- Class alias and rector rules added for backward compatibility List of files: /dokuwiki/inc/Parsing/Parser.php

7958e69808290099292c0703b95d88708f6ebb96 - decouple hardcoded mode names in Eol and Preformatted

Thu, 16 Apr 2026 16:35:56 +0000

decouple hardcoded mode names in Eol and PreformattedEol.php hardcoded ['listblock', 'table'] as modes to skip, andPreformatted.php hardcoded [\*\-] as a negative lookahead for listmarkers. Both embed knowledge that belongs to the respective blockmodes, not to Eol/Preformatted. Adding a new block mode that handlesits own EOL or uses different line start markers would require editingthese unrelated files — a hidden coupling.Listblock and Table now register themselves on ModeRegistry duringpreConnect(). Eol queries getBlockEolModes() and Preformatted queriesgetLineStartMarkers() to build its lookahead dynamically. Each modeowns its own data, and new block modes can participate without touchingunrelated files. List of files: /dokuwiki/inc/Parsing/Parser.php

093fe67e98c0cdb4b73fd46938e49b64971483c2 - updated rector and applied it

Sat, 07 Mar 2026 20:26:13 +0000

updated rector and applied it List of files: /dokuwiki/inc/Parsing/Parser.php

d4f83172d9533c4d84f450fe22ef630816b21d75 - code style: line breaks

Thu, 31 Aug 2023 20:44:40 +0000

code style: line breaks List of files: /dokuwiki/inc/Parsing/Parser.php

177d6836e2f75d0e404be9c566e61725852a1e07 - coding style: control flow whitespaces

Thu, 31 Aug 2023 12:22:35 +0000

coding style: control flow whitespaces List of files: /dokuwiki/inc/Parsing/Parser.php

d868eb89f182718a31113373a6272670bd7f8012 - codestyle adjustments: function declaration braces/spaces

Wed, 30 Aug 2023 15:09:14 +0000

codestyle adjustments: function declaration braces/spaces List of files: /dokuwiki/inc/Parsing/Parser.php

8c7c53b0321a3cd3116b8d3b2ad27863a38dece7 - codestyle adjustments: class declaration braces

Wed, 30 Aug 2023 15:05:28 +0000

codestyle adjustments: class declaration braces List of files: /dokuwiki/inc/Parsing/Parser.php

bcaec9f47d06126b3e653fea89a86d8b6a6cbef8 - Apply rector fixes to inc/Parsing

Tue, 29 Aug 2023 16:14:40 +0000

Apply rector fixes to inc/Parsing List of files: /dokuwiki/inc/Parsing/Parser.php

1b008e8700714b7de7e620d57eccc70c8b206512 - Restore some backwards compatibility for injected handlers

Tue, 14 Jan 2020 23:29:23 +0000

Restore some backwards compatibility for injected handlersSome plugins, for example the move plugin, use their own handler class.We need to give these plugins time to adjust their code.This should restore the functionality of the move plugin. We still needto extract the handler class itself.It also adds another debug method for triggering the deprecation event,since none of the two existing methods are suitable here. ThisdbgCustomDeprecationEvent method should be used sparingly and only wherethe other two don't work.Co-authored-by: Phy List of files: /dokuwiki/inc/Parsing/Parser.php

d4d8fb184de61d888c72a567c003e4eb3c745a17 - moved Parser to Parsing namespace

Fri, 04 May 2018 13:03:58 +0000

moved Parser to Parsing namespace List of files: /dokuwiki/inc/Parsing/Parser.php