Possible bug with dynamic metafield values in theme editor?

Online Store and Theme Development
1

I’m experiencing some weird behaviour with dynamic values referencing metafield text fields. I’m not sure if anything changed, I’m forgetting something or if this is a bug.

I’ve had a field in the theme editor used to render rich text from a metafield, for quite some time (purple) - no issues, it’s rendered like the following in the {template}.json file

"settings": {
   "text": "<p>{{ collection.metafields.namespace.key.value }}</p>"
}

However, currently if I change the dynamic reference or create a new totally identical field, the HTML doesnt compile and the whole field is just rendered as plain text. Thought it was weird, so I checked the value in the json file and now it gets referenced like this:

"settings": {
  "text": "<p>{{ collection.metafields.namespace.key | metafield_tag }}</p>"
}

image
image1304×544 190 KB

image
image340×177 23.1 KB

image
image731×386 71.5 KB

Edit: for reference, manually changing the | metafield_tag to simply .value in the json fixes it. But that’s not really a good solution.

2

I guess it makes sense in the docs and it might be due to the referenced field is a multi_line_text_field containing HTML. Just annoying it worked before (and still does with .value) since it was made that way originally due to easier integration from an old PIM.

Any solutions or do we need to change it to a RTE field and change the PIM integration? :eyes: