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
We migrated from @storyblok/react to use richtext in our project - because of the deprecation warning suggesting to use @storyblok/richtext.
Migration brought several surprises, that some things do not work (e.g. styles passed as string).
Biggest one is - it does not work out of the box, we had to find out that we need to reimplement stuff from the playground.
For DX purposes why does package not contain code in playgrounds by default in the package?
It could e.g. export ReactRichtext, which already has whole basics to make it work.
Or just at least state directly in the readme:
"To make it work with react, implement the code in the playground.", so it could save time for people wondering why things do not work.
The text was updated successfully, but these errors were encountered:
We migrated from @storyblok/react to use richtext in our project - because of the deprecation warning suggesting to use @storyblok/richtext.
Migration brought several surprises, that some things do not work (e.g. styles passed as string).
Biggest one is - it does not work out of the box, we had to find out that we need to reimplement stuff from the playground.
For DX purposes why does package not contain code in playgrounds by default in the package?
It could e.g. export ReactRichtext, which already has whole basics to make it work.
Or just at least state directly in the readme:
"To make it work with react, implement the code in the playground.", so it could save time for people wondering why things do not work.
The text was updated successfully, but these errors were encountered: