[isakovich]

Description

Fix ConfigureJsonSerialisation to preserve existing JsonSerializerOptions instead of overriding them with a new instance. The current implementation instantiates a new JsonSerializerOptions object, discarding any previously configured settings. This change ensures existing configuration is preserved while adding/modifying JustSaying-specific options.

Related Issues

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the Contributing Guide
• I have checked the documentation for relevant guidance
• I have added/updated XML documentation for any public API changes
• I have added/updated tests as appropriate
• My changes follow the existing code style and conventions

Additional Notes

Added tests to verify that JustSaying message properties (Id, Conversation, RaisingComponent, Tenant, Version, TimeStamp) are preserved during serialization and not overwritten, including scenarios where properties come from the request context or publication.

[CLAassistant]

All committers have signed the CLA.

[iancooper]

@isakovich Could you sign the CLA (you keep the IP, you just license it to us)

[iancooper]

Looks good, but I need you to sign the CLA. It protects you, as much as us.

[iancooper]

@isakovich Held up because our build breaks due to an advisory being issued by GHA against Snappier, which our MongoDb drivers depend on. See mongodb/mongo-csharp-driver#1989

Once we can get a fix, and we can get builds again, we can move forward. I assume it will be soon.

[codescene-delta-analysis]

Gates Passed
4 Quality Gates Passed

See analysis details in CodeScene

Quality Gate Profile: Clean Code Collective
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.