.Net: Allow custom serialization options to be passed to TextMemoryPlugin. #7098
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
When
TextMemoryPlugin
gets back multiple results from the memory store during recall, it uses json serialization toturn these multiple results into a single string.
In some cases, this may cause unintended side-affects, e.g. when non-latin script is present in the results,
JsonSerializer
automatically escapes these characters.Adding support for passing custom
JsonSerializerOptions
into theTextMemoryPlugin
to customize the serialization behavior.See #6593
Description
Added optional
JsonSerializerOptions
to theTextMemoryPlugin
constructor.Added example to demonstrate this scenario.
Contribution Checklist