Skip to content
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

Drop requirement for first character to be a pipe |. Pipes seperate columns in markdown. #47

Open
JohnLukeBentley opened this issue Jun 3, 2022 · 2 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@JohnLukeBentley
Copy link

I request the requirement for first character to be a pipe |, be dropped.

For example, the following table is a valid markdown table:

First Header  | Second Header
------------- | -------------
Content Cell  |        Content Cell
Content Cell        | Content Cell

However executing the vscode-markdown-table command "Markdown Table: Format all tables" will have no effect. The extension does not recognize this as a markdown table.

On the other hand the following ...

| First Header  | Second Header
| ------------- | -------------
| Content Cell  |        Content Cell
| Content Cell        | Content Cell

... will be recognized and correctly formatted as following the extension's "Markdown Table: Format all tables" command.

To be clear I think either table should be recognized and formatted.

In most, if not all, of the various markdown standards that support tables with a pipe |, the pipe is a separator of columns, not an opener.

@takumisoft68
Copy link
Owner

I'm trying to allow tables not have begining |.
But unfortunately it's difficult.

Because all implementations in this extention assume that "| must be in the begining of line".

@JohnLukeBentley
Copy link
Author

Thanks @takumisoft68, see what you can do.

@takumisoft68 takumisoft68 added wontfix This will not be worked on enhancement New feature or request labels Aug 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants