Martin Havlišta comments

Results 14 comments of


                                            Martin Havlišta

[Comment] ASP.NET Core Caching in Practice

Thanks the article helped me

Configuration option to change default "send empty value" to true in form data

I reported the same issue for [.NET's Swashbuckle.AspNetCore](https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/1926) and was redirected here.

Add support for nullable reference types

Add `Guard.Hope` `ContractAnnotation` for cases like `Guard.Hope(something != null,` to avoid `Possible null reference return`

The target "CompileTypeScript" does not exist in the project

I got this error message when upgrading from Visual Studio 2022 17.5.3 to 17.7.3 . For my .NET 7 project, adding `` to the csproj file fixed it.

Hot Reload seems not to work properly for ASP.NET Core

todo: create a test case to verify the issue: https://github.com/nhibernate/nhibernate-core/blob/master/CONTRIBUTING.md#creating-a-test-case-to-verify-the-issue

Hot Reload seems not to work properly for ASP.NET Core

That's my feeling as well. Wanted to reproduce it purely using NHibernate and not CoreDdd, but have no time to do that. Hopefully I will do it at some point...

#214 Concurrent validation using RequiredIfAttribute throws NullReferenceException

This was also fixed for `UoN.ExpressiveAnnotations.NetCore`: https://github.com/uon-nuget/UoN.ExpressiveAnnotations.NetCore/pull/33

Concurrent validation using RequiredIfAttribute throws NullReferenceException

PR: https://github.com/jwaliszko/ExpressiveAnnotations/pull/215

Error handler not having access to the original exceptions

@mookid8000 I committed an attempt to fix this: https://github.com/xhafan/Rebus/commit/4be1c8e0a215a3f903566e31da30503e29517a88 Could you please have a look and let me know if you would approve this approach. If yes, I will add...

Error handler not having access to the original exceptions

Yes, I have read it. But it does not work for me as `DefaultRetryStep` news up `ExceptionInfo` directly instead of using `ExceptionInfo` factory, and as a result the error handler...