Custom parsers not installed in specified order?

Lezer
1

I was tinkering with some simple LaTeX extensions and found that the before option doesn’t seem to have any effect on the parsing order. I have the following code:

const BlockLatex = {
    defineNodes: [...],
    parseBlock: [{
        name: "LatexParser",
        parse(cx, line) {
            console.log(line.text);
            return false;
        }
    }],
    before: "FencedCode"
}

When inspecting the JS console, this skips all lines associated with fenced code. Then, to verify that the lines were consumed by the fenced code parser, I edited the function isFencedCode() in editor.bundle.js to always return False; after this change, the lines were not skipped (ie. they would be parsed by my parser).

Am I misunderstanding the function of before or is this a bug? In any case, is there a workaround?

2

It looks like you are putting the before in the wrong place. It should be on the block parser object itself—the one that has the parse method.

3

That did it, cheers!