Kirkey Psalms

It happened to me when I updated the FluentValidation nuget package and look for solution on google. I found none, so I decided to downgrade the FluentValidation version.

I also noticed this bug.

I found the solution. I found this code on github https://github.com/salt-repositories/din-api/blob/97edd4b02a173dc6881cc19b12447c6154a94b98/src/Din.Domain.Middlewares/Mediatr/FluentValidationMiddleware.cs#L30 update to the latest FluentValidation packages: FluentValidation.AspNetCore Version="11.3.0" FluentValidation.DependencyInjectionExtensions Version="11.9.0" public class ValidationBehavior(IEnumerable validators) : IPipelineBehavior where TRequest :...

Been trying to write custom table information for months but no luck. This wasm boilerplate is very hard to understand when we are only relying on EntityTableContext.

Hangfire is one of the best feature of this API. I almost have it on all database procedures and function calls.

This bug still exists up today. Someone have fix on this?

I made it work, 1. uninstall existing codegenerator. 2. test and compile this project. 3. look for the vsix on debug or release folder. 4. install it... Viola!