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
Using the markdoc/next.js library and finding cases where I need to render react in one-off scenarios (e.g. when rendering partial content, and during tests). However the config passed through the transform function of tags differs between what the markdoc/next.js plugin returns and what is returned from Markdoc.renderers.react(content, React) directly.
It seems when directly rendering, the tags render functions are already pre-parsed:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using the markdoc/next.js library and finding cases where I need to render react in one-off scenarios (e.g. when rendering partial content, and during tests). However the
config
passed through thetransform
function of tags differs between what the markdoc/next.js plugin returns and what is returned fromMarkdoc.renderers.react(content, React)
directly.It seems when directly rendering, the tags render functions are already pre-parsed:
Whereas rendering via the plugin they are strings:
Is there a way to pass in the next.js config manually so that we can achieve consistency in both rendering scenarios?
Beta Was this translation helpful? Give feedback.
All reactions