-
-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📎 markdown support #3718
Comments
@AugustinMauroy what's this task for? I don't really understand. Can you please put more description or context into the issue? Unless you really want to work on integrating markdown in Biome, we don't usually create tasks unless someone is already interested or working on it. |
I'd like to try, but I'm no expert on rust, so that's why I'm asking for the spec/roadmap of markdown support. |
We have a contribution guide that should give you the necessary information to start adding a parser inside Biome: https://github.com/biomejs/biome/blob/main/crates/biome_parser/CONTRIBUTING.md Regarding the parsing, I believe we could use that crate, however we still need to map their AST to our CST because we need to own the grammar, and the internal APIs. We've never done this before because all our parsers are built from scratch, so it's something you should explore alone. |
Recently I was digging into biome's architecture and thought I could support this |
I think that in order to support markdown effectively, we will need to have #3334 for formatting code blocks, but I don't think that's necessarily a hard blocker. We could start with a naive parser and formatter that doesn't format code blocks. PRs are welcome, but I expect markdown support will have the same priority as yaml support. |
hello ! i'm not an expert in rust etc ... But what's the next step for markdown support ? |
The lexer and parser is still incomplete. You could take a look in |
Description
We need a specification/roadmap to enable contributors to come and contribute correctly.
Parser :
For the parser I don't think we need to reinvent the wheel, we can use
wooorm/markdown-rs
Formating :
We should follow common mark spec to format correctly
The text was updated successfully, but these errors were encountered: