This is a bug fix release version 2.1.4 of NATS .NET client library. Please also see the potentially breaking change below.
What's Changed
- Added OnNoData Async Func to NatsKVOpts by @darkwatchuk in #439
- Message error processing by @mtmk in #407
New Contributors
- @darkwatchuk made their first contribution in #439
Full Changelog: v2.1.3...v2.1.4
Breaking Change
Because of the way the serialization errors are handled after the change #407 you might see different behaviour in application where serialization errors were potentially not propagated or logged. With this change application code now can check if there were any serialization errors before processing the message:
// Also similar in JetStream consumers and Key/Value watchers
await foreach (var msg in nats.SubscribeAsync<MyEvent>("events.>"))
{
if (msg.Error != null)
{
// handle serialization error
}
else
{
// process message
}
}Nuget Package
dotnet add package NATS.Net --version 2.1.4