Map JSON metadata to Kafka message headers, add unit tests #234
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.
Why
Implements the TODO to propagate event metadata to Kafka headers when the event payload is JSON, enabling downstream consumers to access metadata without parsing the value body.
What’s changed
ContentTypes.Jsonand metadata is present.KafkaHeadersBuilder.BuildHeaders.GetRawText()KafkaHeaderBuilderTests: verifies mapping rules and edge cases.KafkaWriterHeadersTests: integration‑style test with a fakeIProducer<string, byte[]>to assert headers on produced messages.Assert.Thatsyntax.CapturingProducertest double implementing requiredIProducermembers.[OneTimeSetUp]viaReplicationMetrics.Configure(Metrics.CreateUsing());to avoid NREs duringMetrics.Measure.Notes
How to test
dotnet test test/Kurrent.Replicator.Kafka.Tests/Kurrent.Replicator.Kafka.Tests.csprojManual testing
Before:
After:
The manual test was run with the following transform: