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 link block, can any of the link or meta properties under any circumstances (now or in the future) be null or omitted? For the meta object, I assume any of its elements can be omitted, but for the meta.image object, will url always be present and non-null? Are any of the aforementioned properties 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 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 link block, can any of the
link
ormeta
properties under any circumstances (now or in the future) benull
or omitted? For themeta
object, I assume any of its elements can be omitted, but for themeta.image
object, willurl
always be present and non-null? Are any of the aforementioned properties 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 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: