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
Card and Hero both use the <ContentSlot> component from Nuxt Content... or they did. After migrating to a modular approach, I've replaced this with <slot /> in the core module and attempted to overwrite the components in the content module layer.
Unfortunately, whereas these used to respect the formatting of markdown within the components, they are now treating links as a new line entity. Formatting breaks.
Version
0.3.x (Default)
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
These seem to be broken even when I remove the core components entirely and just leave them as they were within the components/content dir of the new content module.
Some kind of dependency conflict kind of issue maybe? We get a lot of warnings about that now, maybe unrelated.
Note: The components unwrap the <p> element. Could that affect this? If <p> were preserved (despite the styling the complications it introduces), would it keep the content bound together?
What happened?
Card and Hero both use the
<ContentSlot>
component from Nuxt Content... or they did. After migrating to a modular approach, I've replaced this with<slot />
in the core module and attempted to overwrite the components in the content module layer.Unfortunately, whereas these used to respect the formatting of markdown within the components, they are now treating links as a new line entity. Formatting breaks.
Version
0.3.x (Default)
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: