since v5.1.5, commit bolt#3122 when number field "mode" is "float" (which is by default), the step is "'any'" by default (note the single quote wrapped by the double quote). This "'any'" value should not be escaped because it breaks when the number field is used within a collection. For instance, bellow is an extract of an "editor-collection" component generated by the backend when using a collection field having "number" field as child, we can see it use a :template prop filled with escaped templates of fields members : ``` <editor-collection :existing-fields='[]' :templates='[{ .. <editor-number ... value=\"\"\n :step=\"&bolt#39;any&bolt#39;\"\n ...' :labels='...' :limit='200' :name=""gallery_slider_images"" :variant=""collapsed"" ></editor-collection> ``` Without applying a |raw filter, the value is double encoded and generates : `:step=\"&bolt#39;any&bolt#39;\"` (which decoded is the same as `:step=\"&bolt#39;any&bolt#39;\"` instead of `:step=\"&bolt#39;any&bolt#39;\"` (which decoded is the same as `:step=\"'any'\"`) This leads to a vue compilation error : ``` [Vue warn]: Error compiling template: ... <editor-number :id='"field-gallery_slider_images-slider_image_set-6241de74820e3-coord_y"' name="collections[gallery_slider_images][slider_image_set][6241de74820e3][coord_y]" value="" :step="&bolt#39;any&bolt#39;" :required="false" :readonly="false" :errormessage="false" :pattern="false" :placeholder="""" ></editor-number> ... - invalid expression: expected expression, got '&' in &bolt#39;any&bolt#39; Raw expression: :step="&bolt#39;any&bolt#39;" ``` However when using number field directly (ie without a collection field) it's was working. Using the |raw filter makes it work in both cases. Note : this regression can lead to data loss when saving broken collections ...

Uh oh!

Uh oh!

🎨 Headless: Make a new base-2019 headless theme #39

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

🎨 Headless: Make a new `base-2019 headless` theme #39