-
-
Notifications
You must be signed in to change notification settings - Fork 235
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
Edit table don't recognize escaped | #933
Comments
Yeah this is a definite bug, but at the moment there's no good workaround because the parsing physically parses out the The escape scenario can be handled somewhat easily by transforming the string and resetting after parsing, but the use case of Couple of things come to mind:
The first would work if Markdig supports peeling out the cells and that would be idea. The latter is problematic because it might render away some of the raw Markdown Markup you can potentially use (ie. bold/italic/code etc.) Have to give this one some thought. |
So after a little experimenting I can make the first escaped scenario work with a relatively simple fix using text replacements: However, the |
If escape using \ works then that's the preferred way of doing it! |
Well, yes, it's preferred in your use case but it may be a requirement for another use case (like the second example). The fix for your exact issue will go into the next update. I'll give some more thought to how to address the embedded code scenario. |
So this has been fixed for 2.4.6.4 for the escaped pipe (ie. The |
I have a table that has a pipe character | in it's value
If I escape the character with an backslash then it looks OK in the preview.
But if I Edit Table then it takes the escaped pipe as an actual pipe and I get a new column.
I also tried to mark the pipe as code but I got the same result!
My test table
// Anders
The text was updated successfully, but these errors were encountered: