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 Markdoc nodes docs, I expect content, language, and process props in my Svelte component. But I also receive a default slot, which seems to contain the same as content. Since my Fence component does not make use of the default slot, I see a console warning <Fence> received an unexpected slot "default"..
I can silence the warning, but I wonder why I am receiving the default slot.
To Reproduce
I have no public reproduction. But this console warning should be visible with the demoFence component mentioned above. It does not use a slot.
Expected behavior
Just pass content, language, and process?
Screenshots
n/a
Desktop (please complete the following information):
n/a
Smartphone (please complete the following information):
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Describe the bug
I am building my own
Fence
component, similar to the one from the demo: https://github.com/TorstenDittmann/svelte-markdoc-preprocess/blob/main/apps/demo/src/lib/nodes/Fence.svelte.According to the Markdoc nodes docs, I expect
content
,language
, andprocess
props in my Svelte component. But I also receive a default slot, which seems to contain the same ascontent
. Since myFence
component does not make use of the default slot, I see a console warning<Fence> received an unexpected slot "default".
.I can silence the warning, but I wonder why I am receiving the default slot.
To Reproduce
I have no public reproduction. But this console warning should be visible with the demo
Fence
component mentioned above. It does not use a slot.Expected behavior
Just pass
content
,language
, andprocess
?Screenshots
n/a
Desktop (please complete the following information):
n/a
Smartphone (please complete the following information):
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: