Having trouble opening a document saved by the editor

[eltiare]

I'm using a component to get the whole document to save when the user submits the form. The codebase for the relevant part is pretty short, so here's the gist of the editor component and its output:

https://gist.github.com/eltiare/c101eccef99e20a6b99bc90929537125

I'm getting errors saying that type is undefined, which of course everything below the top level the attribute does not exist on any of the objects. Instead, the name of the attribute is object. I've narrowed it down to this, but I am not sure what the proper behavior is supposed to be - or if I'm getting bitten because I am not getting the current document in the correct way.

[eltiare]

Looks like Slate has renamed the attribute/field name. As such creating the document works ok and loading it does not. I'm assuming the validation happens on this project's side? I'll dig into this later because it's really annoying.

[gabrielrtakeda]

@eltiare the problem is exactly that. The slate has renamed the state object attribute name.. we have this function that treats the differences of slate's state object attribute name from v0.25.3 to v0.31.3 but, it seems that slate has changed another fields... The intention of this "migration" function is not to keep inside of slate-editor itself but, otherwise, decouple it into a separated module that handle the compatibility of slate's state object properties...

We already have the issue below, to keep some "migration" function that normalize the slate's state object to the latest version:

• Decouple Slate state object migration logic from project Decouple Slate state object migration logic from project #55