.Net: Bug: Inconsistent usage of JsonSerializer options

[Ilia-Kosenkov]

Hi! I am exploring semantic kernel and was looking into specifying JSON serialization options for my plugins. I stumbled upon this doc https://github.com/microsoft/semantic-kernel/blob/main/docs/decisions/0060-jsos-integration.md and followed it. However, I observed that the tool call results in chat history are serialized with some default behavior different from what I expect. I debugged deep into the framework and found that the function result is serialized here with the default JSON configuration. Which AFAIK I cannot influence.

semantic-kernel/dotnet/src/InternalUtilities/connectors/AI/FunctionCalling/FunctionCallsProcessor.cs

Lines 503 to 516 in 2a5fa44

	return JsonSerializer.Serialize(functionResult, s_functionResultSerializerOptions);
	}
	/// <summary>
	/// The <see cref="JsonSerializerOptions" /> which will be used in <see cref="ProcessFunctionResult(object)"/>.
	/// </summary>
	/// <remarks>
	/// <see cref="JsonSerializer.Serialize{TValue}(TValue, JsonSerializerOptions?)"/> is very likely to escape characters and generates LLM unfriendly results by default.
	/// </remarks>
	private static readonly JsonSerializerOptions s_functionResultSerializerOptions = new()
	{
	Encoder = JavaScriptEncoder.UnsafeRelaxedJsonEscaping,
	};
	}

Are there any plans to allow configuration of this options as well? Can it affect chained tool calls when using a history object?