Checklists/todos are highlighted as such without a trailing slash about markdown

[marijnh]

Guess it doesn't matter too much either way. I've merged the PR.

[acnebs]

I've gone ahead and made a PR (since this is a dead simple change) if you're happy with this @marijnh.

[marijnh]

I'm wondering if we might also want to parse lines with just - [ ] as tasks lists (not following the spec) in order to make this less confusing to people typing this in an editor. (This package is more about editor tooling than about fully correct Markdown parsing.)

[acnebs]

Yeah, I was thinking about that as well, and was a bit conflicted. On the one hand if the user actually follows through, it is less jarring for them if the task list is marked as such as soon as they type the closing bracket. However, it does seem desirable to highlight things according to the spec because otherwise it is slightly misleading. A user types - [ ], it is highlighted by lezer as a task list, but then when they actually throw that into basically any markdown renderer with GFM support, it will not be rendered as such.

That being said, for my use-case in particular, I think the best solution is what I've done in the PR, as with an "auto-continue list functionality" (or any sort of "we start the list for you" functionality) a space can be automatically included at the end (- [ ] ), and that gets highlighted even though there is technically no content afterwards yet. This is less jarring than if you required content after the whitespace. But we still don't want to display it as valid without the whitespace, because we want users to know that it is wrong while they are editing.

[acnebs]

Thanks!