If you add shortcode syntax ({[ ]}) to the Documentation field in the new Obsidian LavaShortcodeDetail block, then when you go to edit the shortcode it defaults to Code Editor without allowing it to show the visual editor.
Before save:
After save:
I often use this Documentation field for quick copy/paste references on how to use the shortcode.
Actual Behavior
The visual editor doesn't show if there is any shortcode syntax ({[ ]}) present.
Expected Behavior
I would expect that using shortcode syntax in the Documentation field would show the rendered output in the visual editor (the non-Obsidian block did).
Steps to Reproduce
On the prealpha site, go to Settings, then click on Lava Shortcodes
Click the + icon to create a new shortcode
Name it test, make the shortcode test, mark it inline, and put test in the shortcode markup (this is irrelevant but they are required fields)
In the Documentation field, add the shortcode syntax: {[ test ]}
Save the shortcode
Find the shortcode in the list and open it, then click Edit
Notice how the Documentation field only shows code editor without the ability to switch to visual editor
Issue Confirmation
[X] Perform a search on the Github Issues to see if your bug or enhancement is already reported.
[X] Reproduced the problem on a fresh install or on the demo site.
Description
If you add shortcode syntax (
{[ ]}
) to the Documentation field in the new Obsidian LavaShortcodeDetail block, then when you go to edit the shortcode it defaults to Code Editor without allowing it to show the visual editor. Before save:After save:
I often use this Documentation field for quick copy/paste references on how to use the shortcode.
Actual Behavior
The visual editor doesn't show if there is any shortcode syntax (
{[ ]}
) present.Expected Behavior
I would expect that using shortcode syntax in the Documentation field would show the rendered output in the visual editor (the non-Obsidian block did).
Steps to Reproduce
On the prealpha site, go to Settings, then click on Lava Shortcodes
Click the + icon to create a new shortcode
Name it
test
, make the shortcodetest
, mark it inline, and puttest
in the shortcode markup (this is irrelevant but they are required fields)In the Documentation field, add the shortcode syntax:
{[ test ]}
Save the shortcode
Find the shortcode in the list and open it, then click Edit
Notice how the Documentation field only shows code editor without the ability to switch to visual editor
Issue Confirmation
Rock Version
Rock McKinley 17.0 (1.17.0.30)
Client Culture Setting
en-US