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
For a valid checklist block, under any circumstances (now or in the future) :
Can the items property be null or omitted?
Can any array element in items be null?
Can the text or checked properties of any item be null or omitted?
Or are all of the aforementioned properties/values guaranteed to always be present and non-null for this block to be valid?
Context: I'm a back-end .NET developer needing to parse Editor.js documents. The readme lists all of the aforementioned properties/values but does not explicitly guarantee that they will always be present and non-null. Back-end deserialization/parsing in strongly typed languages would be easier with some guarantees about which properties can and can not be null/omitted. (Ideally, any such guarantees should be added to the readme to ensure they are formalized and kept in the future.)
The text was updated successfully, but these errors were encountered:
For a valid checklist block, under any circumstances (now or in the future) :
items
property benull
or omitted?items
benull
?text
orchecked
properties of any item benull
or omitted?Or are all of the aforementioned properties/values guaranteed to always be present and non-
null
for this block to be valid?Context: I'm a back-end .NET developer needing to parse Editor.js documents. The readme lists all of the aforementioned properties/values but does not explicitly guarantee that they will always be present and non-null. Back-end deserialization/parsing in strongly typed languages would be easier with some guarantees about which properties can and can not be null/omitted. (Ideally, any such guarantees should be added to the readme to ensure they are formalized and kept in the future.)
The text was updated successfully, but these errors were encountered: