Instructions
Refactor a Markdown parser.
The markdown exercise is a refactoring exercise.
There is code that parses a given string with Markdown syntax and returns the associated HTML for that string.
Even though this code is confusingly written and hard to follow, somehow it works and all the tests are passing!
Your challenge is to re-write this code to make it easier to read and maintain while still making sure that all the tests keep passing.
It would be helpful if you made notes of what you did in your refactoring in comments so reviewers can see that, but it isn't strictly necessary.
The most important thing is to make the code better!
Refactoring
The implementation in Markdown.roc already passes the tests.
Refactor it while preserving its behavior and the parse : Str -> Try(Str, _) interface.
Return Ok(html) on success and propagate any parsing errors with Err(...).
This exercise covers a small Markdown subset, not the full Markdown specification.
The tests define the behavior to preserve, including how blank lines and unmatched emphasis markers are handled.
Hints
Show hints
Look for repeated logic, deeply nested conditions, cryptic names, and unnecessary mutable state.
Consider separating line classification, inline emphasis, and HTML rendering.
The roc-parser package is available as parser in the test app if you want to use it.
Parser.one_of, Parser.many, and Parser.between can help combine small parsers.
A solution using ordinary string and list functions is equally welcome.
