Migrating from rich-content
This section is intended for users of the legacy RichContentEditor & RichContentViewer API.
#
MotivationThe motivation behind this project is to provide a better user experience for rich-content
consumers.
The core idea is to wrap the RichContentEditor
/RichContentViewer
with a "transparent" wrapper which would provide convenient default configuration to its child component, while maintaining it fully backwards-compatible for existing applications. The three main goals are:
- simpler API and configuration
- less breaking changes
- reduced amount of code duplication between consumers via providing a default implementation
#
Getting started#
Existing consumersExisting consumers can gradually integrate Ricos into their code. The Ricos wrapper provides a configuration to its children based on its own properties. Any props that are passed directly to the child override the wrapper's ones.