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
Right now, in all editors, you can use element or data as the first parameter. The problem is, that, in many cases, you want to use the element for your existing DOM, but use data from the database. The problem is even bigger when you use for instance React integration where we have no good way to inject HTML data to DOM.
it will create an undo step during the initialization,
it will break the collaboration if the collaboration plugin is used because you need to have initial data available in the collaborative editor during the editor initialization (this is the moment when the editor decides if local or server data should be used).
This is why we decided that initialData configuration should be introduced.
Right now, in all editors, you can use element or data as the first parameter. The problem is, that, in many cases, you want to use the element for your existing DOM, but use data from the database. The problem is even bigger when you use for instance React integration where we have no good way to inject HTML data to DOM.
Because if it many integrations uses:
but this is wrong, because:
This is why we decided that
initialData
configuration should be introduced.initialData
will be used instead of elements HTML.Exception will be thrown, such configuration does not make sense.
In the future we plan to move also source element to the configuration:
But since this is a bigger (and breaking) change, we agreed to pospond it and do it later.
The text was updated successfully, but these errors were encountered: