The json_as_string and yaml_as_string data types were added as types that should be kept as strings and not parsed. So the logic below appears reversed from what's intended.
\Drupal\ai\Plugin\AiDataTypeConverter\JsonDeserializer::appliesToDataType()
if ($data_type !== 'json_as_string') {
return AppliesResult::notApplicable('The data type is not JSON.');
}
return AppliesResult::applicable();
\Drupal\ai\Plugin\AiDataTypeConverter\YamlDeserializer::appliesToDataType()
if ($data_type !== 'yaml_as_string') {
return AppliesResult::notApplicable('The data type is not YAML.');
}
return AppliesResult::applicable();
Reverse it
Active
1.2
AI Core module
I'm going to leave that failing test until I can get another set of eyes that this needs to switch.
Maybe the names of the types are bad (string_to_json, string_to_yaml?) and we should change them, but it should work that the default of a normal string that happens to be json or yaml, should not be encoded and that is something you have to opt-in to, by selecting the json_to_string.