v3.2.0

What's new

Possible breaking change: Reverting use of Microsoft.Extensions.DependencyInjection namespace from v3.0.0 to follow Microsoft guidance; all affected namespaces are adjusted to W4k.AspNetCore.Correlator (extension method for configuring and registering correlator to DI)

No functional change 🤷

v3.1.0

What's new

• Prevent log injection by sanitizing correlation ID value before logging (when logging is enabled) (base alphabet with few extra symbols allowed, max length 80 chars - not possible to configure)

v3.0.0

What's Changed

• adding targets net7.0 and net8.0
• dropped support for netstandard2.0 and netstandard2.1
• removing direct dependency on Microsoft.AspNetCore.Http.Abstractions

Adding .NET 8 target and other teeny-tiny changes on #60

Full Changelog: 2.3.0...3.0.0

Breaking changes

Apart of dropping netstandard from targets, few minor changes were made:

• DI extensions moved to Microsoft.Extensions.DependencyInjection namespace
  • leaving old extension methods on its original place with [Obsolete] attribute
  • may cause conflicts when upgrading - simply remove W4k namespaces from usings
• CorrelatorOptions.ReadFrom exposes List<> instead of ICollection<> (should not break anything 🤞)
• Throwing ArgumentException when input string is empty, and ArgumentNullException when input is null from various places
  • previously only ArgumentNullException was thrown

v2.3.0

What's new?

• micro-optimization:
  • using throw helper instead of throwing exceptions directly (to please JITter)
  • passing emitter by state when registering HttpResponse.OnStarting callback, avoiding capture/function allocation

Fixes

• throwing ArgumentNullException when configuring correlator using correlatorBuilder.WithValidator(...) and passing null validator

Other changes

Unrelated to binary distribution:

• dropping netcoreapp3.1 sample app
• update BenchmarkDotNet

v2.2.2

What's new?

• directly targeting .NET 6.0

v2.2.1

New stuff

• ICorrelatorBuilder.WithValidator throws when attempting to register validator second time - only one validator is allowed (unchanged behavior), throwing explicitly

v2.2.0

New features

• Possibility to validate value of correlation header
• Simple implementation CorrelationValueLengthValidator provided to check value length

Breaking changes

• AddDefaultCorrelator now returns ICorrelatorBuilder so you can continue with registering validator

Other

• Adding PublicAPI metadata

(v2.2.0-preview1 & v2.2.0-preview2)

v2.2.0-preview2

New behavior

• CorrelationValueLengthValidator considers correlation ID valid not only when its length is lower or equal to given limit, but value must not be null or empty string

Other

• Adding PublicAPI metadata

v2.2.0-preview1

New features

• Possibility to validate value of correlation header
• Simple implementation CorrelationValueLengthValidator provided to check value length

Breaking changes

• AddDefaultCorrelator now returns ICorrelatorBuilder so you can continue with registering validator

v2.1.1

Bugfix

• fixing issue after release 2.1.0 where DI threw when attempting to register CorrelatorHttpMessageHandler (ctor argument changed and PropagationSettings were not registered)