RichTextEditor now will not reset the editor's document content when its content prop changes. This should make the component more generally flexible, with the option for users to customize when/how they want to setContent. See the new README section on "Re-rendering RichTextEditor when content changes" for more details and alternative approaches. (This is all related to the discussion here https://github.com/sjdemartini/mui-tiptap/issues/91#issuecomment-1629911609.)
RichTextReadOnly now will reset the editor's document content when its content prop changes. This is how it should've worked all along, since it's read-only and should be treated as a more "pure" renderer.
README has been updated with more details about when/how to use these two components.
There are additional tips on editor extensions in the README, in a slightly improved format.
RichTextEditornow will not reset the editor's document content when itscontentprop changes. This should make the component more generally flexible, with the option for users to customize when/how they want tosetContent. See the new README section on "Re-rendering RichTextEditor when content changes" for more details and alternative approaches. (This is all related to the discussion here https://github.com/sjdemartini/mui-tiptap/issues/91#issuecomment-1629911609.)RichTextReadOnlynow will reset the editor's document content when itscontentprop changes. This is how it should've worked all along, since it's read-only and should be treated as a more "pure" renderer.