Before updating from 1.5.* to 1.6.3 it was like that:
Now it like that
It was only one relativly simple way to do nested tables
Return it back pls
Before updating from 1.5.* to 1.6.3 it was like that:
Now it like that
It was only one relativly simple way to do nested tables
Return it back pls
Sorry, I don’t understand what this is. Please, repost this. Make sure you follow the bug report template and attach a copy of note where this happens. Thanks
What is unclear?
There is such an markdown-code:
> [!quote]+ | | |
> | --- | --- |
> | asdasdasd | asdasdasd |
>
>
>
> | COL1 | COL2 |
> | --- | --- |
> | WASD | tmp |
>
previously, a table was rendered in the header as here (succeeded):
But now after new obsidian version - table is not being rendered in callout header right now (wrong):
It’s needed to return it as it was
We do not support this syntax:
> [!quote]+ | | |
> | --- | --- |
> | asdasdasd | asdasdasd |
>
>
>
> | COL1 | COL2 |
> | --- | --- |
> | WASD | tmp |
>
You are tying to force Obsidian into doing something that was not designed to do. We do not support having the table begin the title of the callout.
you can do this:
> [!quote]+
> | col1 | col2 |
> | --- | --- |
> | asdasdasd | asdasdasd |
>
I can’t wait for the implementation of the functionality of nested tables. When will it be? In 10 years?
Okay, I get it, this update is just terrible, you broke:
One update!
And when asked to SIMPLY RETURN IT AS IT WAS, there are only excuses (pretenses/silent topic closures), on all points
That’s just terrible. That’s it, I won’t distract you with my requests anymore, I’m rolling back the update, I’m not downloading new ones - break the project, I’m not distracting
I am sorry but this syntax that you use here:
> [!quote]+ | | |
> | --- | --- |
> | asdasdasd | asdasdasd |
>
>
>
> | COL1 | COL2 |
> | --- | --- |
> | WASD | tmp |
>
It is not in the docs, I am not even sure what it is supposed to do. The first line of callout is for an optional title, not for a table.
Perhaps you found a quirk of the parser and built a workflow around it that eventually broke down.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.