* Reinstantiate editor on changes
We can't dynamically update the content, so we have to recreate the Editor whenever something changes (page loads and updates)
* Fix import
@tiptap/core is different than @tiptap/react, who knew
* Added several Tiptap components
* Added a Remix icon that isn't in remixicon-react
* Add colors for highlights
* Add ToolbarButton component
This is to standardize adding Toolbar icons so it wasn't a miserable mess in the Editor file
* Add extensions and implement ToolbarButton
* Remove unused code
* Use party prop and add keys
We always want to use the party in props until the transformer work is done and our source of truth is more reliable.
Also, we are using keys to ensure that the component reloads on new page.
* Component cleanup
* Always use props.party
* Ensure content gets reset when edits are committed
Here, we do some tactical bandaid fixes to ensure that when the user saves data to the server, the editor will show the freshest data in both editable and read-only mode.
In the Editor, its as easy as calling the setContent command in a useEffect hook when the content changes.
In the party, we are saving party in a state and passing it down to the components via props. This is because the party prop we get from pages is only from the first time the server loaded data, so any edits are not reflected. The app state should have the latest updates, but due to reasons I don't completely understand, it is showing the old state first and then the one we want, causing the Editor to get stuck on old data.
By storing the party in a state, we can populate the state from the server when the component mounts, then update it whenever the user saves data since all party data is saved in that component.
* Fix build errors
Justin Edmund
83bebdb0c2