Use case or problem
It’s well known that Obsidian has lots of room for improvement for how it handles tables. Tables in Obsidian require very specific formatting, which is very easy to mess up and confuse users on why their tables don’t render.
I’ve had this issue myself a few times, where I’d stare at every single character in tables to see why it wouldn’t render, including recently when Obsidian updated and started requiring spaces above Markdown tables, to conform to Markdown standard(s).
Proposed solution
Let’s say I have a proper table like this:
And I change gfx.webrender.all to remove the second `, then it looks like this:
Obsidian could Scan the note continuously or periodically (like an IDE does for syntax & code errors) to see if any of the text is supposed to be or resembles the syntax for a table, and show error messages for why it doesn’t render a table, showing / mentioning missing or improper characters, or when characters like `s for inline closed aren’t closed.
Perhaps it could show a tooltip pointing to the line with the error, with a message like “missing closing character on this line, character 20.”
