You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think it's part of the spec in any way for EXTENSION_PIPE_TABLE, at least as shown here, but I usually find myself using markdown tables with empty cells. I use treesitter to navigate them (jumping to the next pipe_table_cell, but these empty cells are not detected in any way. For example:
As you can see, if jumping between pipe_table_cell, we would jump directly from the cells 1 to 3. Is this something possible or that doesn't break any of the standards?
The text was updated successfully, but these errors were encountered:
I agree, the output should contain a node even for empty cells. The problem is that nodes in treesitter cannot be empty (unless they're parsed by the "external scanner"). Cell nodes at the moment do not contain the | delimiter, which I think makes sense, so they are indeed empty sometimes (or only contain whitespace).
I think this is quite easily fixable by moving the cell node to the external scanner. I'll try to do that (but don't expect a solution to soon, I'm a bit busy at the moment)
I don't think it's part of the spec in any way for
EXTENSION_PIPE_TABLE
, at least as shown here, but I usually find myself using markdown tables with empty cells. I use treesitter to navigate them (jumping to the nextpipe_table_cell
, but these empty cells are not detected in any way. For example:The tree for this table is:
As you can see, if jumping between
pipe_table_cell
, we would jump directly from the cells1
to3
. Is this something possible or that doesn't break any of the standards?The text was updated successfully, but these errors were encountered: