Paste this into a note:
> ```ts
> for (const el of array) {
> console.log('Hello world')
> }
> ```
Instead of looking like this (a code block in a block quote):
for (const el of array) { console.log('Hello world') }
It shows up like this in Live Preview.
Licat confirmed that it is a parser bug.
Quote:
> Add the `-Z` (aka `--null`) flag to `grep`, and the `-0` (also aka `--null`) flag to `xargs`. This will output NUL terminated file names, and tell `xargs` to read NUL terminated arguments.
>
>eg.
>
> ```shell
> grep -irlZ $schema $WORKDIR/ | xargs -0 sed -i 's/'"$schema"'/EXI1/gI'
> ```
The above note should be rendered properly in live preview mode, as the same as in the preview mode:
The code block within the block quote is not rendered properly.
RECOMMENDATIONS:
none
No
As a workaround, I’ve started to make my quotes admonitions.
I.e. adding > [!quote] at the start of the quote block solves the problem. I.e. code blocks are rendered ok. But then full quote is an admonition, which is not what everybody would like.
Hi, any update on this FR? I’ve notices this as well, I thought on first instance that the code block weren’t working inside quote blocks, but then I switched to read mode and it’s properly rendered…
