Hi @achillis. That's right, all the content of fields which type is array:array:string is type forced to string, so html content is stripped. Thus, more than a bug, this post might be a feature.

Maybe each field in the subset should be received according to its definition. In such case, a new type array:array:mixed would make sense.

Regards!

That sounds good and does make more sense. Thanks.

Is this feature in the pipeline?

@achillis it's still under discussion.

Any feedback on this yet?

still in progress