Number field issue when used inside a structured text block

We have an issue with a block type, which contains a number field, that was previously working fine. I’ve done a simple recreation in a 2nd project:

  1. Create a block type with a single number field
  2. Create a model with a structured text field that allows the block
  3. Create an instance of the model and try to add the block type and set a number in the field

Instead of seeing the number entered, it is replaced with [Object object] and therefore fails validation.

This doesn’t happen with number fields directly in the model, nor when the block is used within a Modular Content field, only when the block is used within the Structured Text field.

Hello @james1 and welcome to the community!

We just shipped a fix for this!

Thank you for your detailed report :slight_smile:

1 Like