You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're stuck in the past on a certain hugo version (0.55.5. It's unclear how easy it is to update the version, but it probably requires fixing a few templates.
At least one issue that'll be resolved by upgrading is code blocks in lists. As of now,
1. foo
```
some code
```
2. bar
will not render correctly. The markdown renderer was replaced in a later version of hugo.
(The old version probably has implications on being able to use current hugo plugins? But I'm not sure. Came to mind wrt #3664.)
The text was updated successfully, but these errors were encountered:
* website: bump hugo, updated templates
For some reason, the "and" trick to step around undefined values no longer
worked. So now, we're wrapping {{ if }} conditionals instead: the outer one
checks that the value is defined, the inner one asserts something on its
value.
* live-blocks/preprocess: add wrapper div, remove newline
Somewhere between 0.55 and the most recent version, Hugo stopped emitting
that div on purpose for languages it didn't know.
Since we depend on it for further processing, we're adding it back.
Also, a trailing newline for code elements was introduced, and that broke
our codemirrors integration -- every code entry would be folllowed by an
empty line. Now, we're removing that in the same preprocess step.
* website: fix info|danger blocks
* website/config: trust markdown to include html
Fixes#3787.
Signed-off-by: Stephan Renatus <[email protected]>
We're stuck in the past on a certain hugo version (0.55.5. It's unclear how easy it is to update the version, but it probably requires fixing a few templates.
At least one issue that'll be resolved by upgrading is code blocks in lists. As of now,
will not render correctly. The markdown renderer was replaced in a later version of hugo.
(The old version probably has implications on being able to use current hugo plugins? But I'm not sure. Came to mind wrt #3664.)
The text was updated successfully, but these errors were encountered: