-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Node tableHead not parsed correctly #14
Comments
Welcome @diervo! 👋 A few things:
I suspect your question is an XY problem, you probably want to do something with a remark plugin? |
This comment has been minimized.
This comment has been minimized.
Hi @ChristianMurphy, I understand a little bit about syntax trees, as I have worked quite a lot in the past with @wooorm while he was building The reason I filed the issue was mostly to get the team's take on whether having a new node of type Seems that micromark is already disambiguating and tokenizing it correctly, so seemed like a pretty straight-forward change in the AST generation There are a lot of precedents of this disambiguation on similar "ast-like abstractions" (ex. ProseMirror), and it will allow for the user to configure whether or not they want to assume that the first row is a header or not. |
Thanks for the clarification @diervo! Would you be interested in drafting an RFC PR with your thoughts? |
It will be hard for me to find the time, not necessarily for the RFC but to help push it through the whole process (I been in enough standardization comittes to know that it takes a village... xD) But knowing that you are open to it, I will do my best to eventually find some time. FWIW I think this change could be non-breaking if we default to the current behavior and add some options on top, but certainly it will require some non-trivial debate. |
This change would go into mdast. And then be pulled in everywhere else. There is indeed no I think ASTs should be simple. It should be hard to make mistakes in ASTs. With different names for these node types, it’s easier to accidentaly inject a Finally, as the ASTs and projects grow older, I think it’s sensical to be more stable. What use cases does this really improve? |
Initial checklist
Affected packages and versions
[email protected]
Link to runnable example
No response
Steps to reproduce
The following code should produce a tableHead node:
Expected behavior
Runtime
Node v16
Package manager
npm v7
OS
macOS
Build and bundle tools
Vite
The text was updated successfully, but these errors were encountered: