Daniel Gonzalez Garcia

> #1152 > Might be relevant. It is still open but there are some work arounds in it. Uhm, I am not sure it is relevant as we do not...

Does this also fix the issue when making a GET request that responds with a 204? Right now, our endpoint calls that return 204 are failing because of the inclusion...

Our team is being affected by this unexpected behavior (middlewares and events not executed when having emitted an event to a dynamic namespace for which a socket has not connected...

Any updates on this? A rough estimate when we can expect this feature? It would be a very useful feature for our team as we have implemented Sparkplug communication for...

Provide snippet with `CanonicalMoneyConverter`. Roughly: ```csharp public class MoneyConverter : JsonConverter { public override Money Read(ref Utf8JsonReader reader, Type typeToConvert, JsonSerializerOptions options) { throw new NotImplementedException(); } public override void...

I cannot use this package in my typescript ESM project because this issue has not been released.

Roughly related to this issue (which I am solving myself with the delegation of all `.Parse()` overloads to the underlying type) comes the fact that the already generated `.TryParse()` do...

I just found a new inconsistency with normative `.TryParse()` on structs (in my case a record struct) and that has to do with value objects relationship with `default` instances (or...

add support for parsing `ReadOnlySpan`