Remove rich_content_editor v-model
The previous v-model approach broke the contract expectation in that under the hood, rich_content_editor uses the toast-editor component that only takes an initial value and internally manages its state. I also cleaned up edit_area by properly encapuslating parse_source_file's concerns in it where previously they crossed over
Showing
Please register or sign in to comment