New editor is not backwards compatible

[Phil (Phil Snow)]

Hi Thomas,

I'll be happy to help with this, and I really appreciate the feedback.

@thomas3

• Default boolean values used to have their default values when we fetch them from the api. Now, if you don't change the value of the boolean it will just return "null" in the api. This is unexpected behaviour.

So this is a known bug not related to the new builder, but one the team hopes to tackle soon.

[Bug] Select & boolean fields return null rather than initial value

Same problem, using slice-machine-ui 1.19.1 Please fix this bug.

@thomas3

• We have a model called "Participant", and the first field is "First name". We used to be able to create multiple instances of this model with the same first name, but when using the new editor, it looks like it's using this for some kind of unique ID. When trying to create a second instance with the same first name, I can't save the model anymore ("error": "document_uid_conflict")

This is strange behaviour; if you have a screenshot of this, it would be really useful if it's a bug in the new builder. Usually, this should only happen on a UID field. If the "First name" field is a UID field, then this is the expected behaviour.

@thomas3

• There's also no more way to publish a document after making an edit to it and saving it.

I'm not quite sure what you mean here. Can you send me a screenshot for this as well?

@thomas3

Is it possible to switch our whole account back to the old legacy editor?

I'll be very happy to switch you over to the legacy editor. Can you tell me which repo that is for so I can process this for you?

Thanks.