Issues caused by attributes with undefined values #4111
Labels
package:engine
resolution:wontfix
This issue will not be fixed because the team decided that for given reasons it does not make sense.
status:discussion
type:improvement
This issue reports a possible enhancement of an existing feature.
#500 showed that it may happen that a slightly broken converter will try to create an element in the model which has some attribute but the value of this attribute is
undefined
.There's a range of issues which such attributes may cause. It can't be stringified (
JSON.stringify()
will skip it) so it may blow up collaborative editing servers. It causes issues on conversion to the view because (that's my hypothesis) proper attribute elements are created but they are not merged later on for some reasons (the second part of #500).I wonder if we shouldn't reject such attributes at some point because such issues may be hard to track. Perhaps, once will have "one API to rule them all", the right place will be in the model writer? Or perhaps this should be done directly in
Node
?The text was updated successfully, but these errors were encountered: