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
According to the spec: "Each paragraph in your recipe file is a cooking step. Separate steps with an empty line."
It provides the following as an example:
A step,
the same step.
A different step.
Pasting that text in the playground, I expect to see 2 steps but instead see 3:
I also see this behavior in the plugin and CLI, so I figure this is the right place to post it. Not sure if this is where the bug is though.
To throw my 2c in pre-emptively, the spec is wise on this IMHO. A good markup language allows for semantic line feeds, essentially allowing the user to break elements down into atomic thoughts being their own lines which is great for editing and making git history easier to interpret, without effecting the presentation.
EDIT:
I should add my cooklang obsidian version is 0.3.0.
And for cooklangcli version I tried both the main branch and 0.8.0, but looking at it again it looks like neither are using the latest version of this crate which is 0.9
The text was updated successfully, but these errors were encountered:
Each paragraph in your recipe file is a cooking step. Separate steps with an empty line.
This has been added to the spec recently.
This parser has supported it since the beginning but only in the last version it has been enabled by default. So any aplications that have not been updated in the last couple of weeks will probably use old way of breaking the recipe into steps.
Also, I'm pretty sure neither that playground nor the obsidian plugin use the rust parser.
Yep, just wanted to confirm that the playground you mentioned is based of cooklang-ts parser which is (slowly) being migrated to use wasm cooklang/cooklang-ts#27. You can use other playground https://cooklang.github.io/cooklang-rs/ based on rust parser.
According to the spec: "Each paragraph in your recipe file is a cooking step. Separate steps with an empty line."
It provides the following as an example:
Pasting that text in the playground, I expect to see 2 steps but instead see 3:
I also see this behavior in the plugin and CLI, so I figure this is the right place to post it. Not sure if this is where the bug is though.
To throw my 2c in pre-emptively, the spec is wise on this IMHO. A good markup language allows for semantic line feeds, essentially allowing the user to break elements down into atomic thoughts being their own lines which is great for editing and making git history easier to interpret, without effecting the presentation.
EDIT:
I should add my cooklang obsidian version is 0.3.0.
And for cooklangcli version I tried both the main branch and 0.8.0, but looking at it again it looks like neither are using the latest version of this crate which is 0.9
The text was updated successfully, but these errors were encountered: