Very good content! Congratulations. How can I validate a MapGet with query parameters ? The idea is validate allowed (valid) combinations of five parameters included in the query
What’s the best way to validate a recipients bank account details for different countries? Some have swift codes and others have iban numbers, others have account name and branch code. But they all use create recipient endpoint. Should you split the endpoint? Or use a flag in the validation logic? Or can you pass some kind of schema to the validation method, ie. The request should match a certain schema 100%
On one hand its a very neat implementation, but on the other there is a bit too much auto-wiring magic for my liking. Not sure I would go with this approach.
Can you explain how its "too much auto wiring magic" when you have to explicitly add WithRequestValidation to the endpoints? Or are you talking about the auto registration of the validators using builder.Services.AddValidatorsInAssembly()? If it is this one, this is a very common thing that .NET projects do, register things by convention. If you are using Controllers, .NET has a builder.Services.AddControllers() method which will do the exact same thing, register all controllers to the DI container etc.
your videos are definitely more useful than long&empty chapsas videos. thanks
Thanks, glad you like them!
Fantastic tut, cannot get any better from here. Thank you for your amazing work!
Glad you found it helpful!
Amazing stuff, to the point and very useful indeed!
Glad it was helpful!
Great video: to the point and full of real life stuff while keeping it simple. Awesome. Subscribed!
Thanks for clearly explanation!
Great video. Keep it up.
Thanks!
Well explained and helpful. Any idea how do i use ruleset with the validationextension.
How would you validate query parameters that are int's and strings?
Very good content! Congratulations.
How can I validate a MapGet with query parameters ? The idea is validate allowed (valid) combinations of five parameters included in the query
What’s the best way to validate a recipients bank account details for different countries? Some have swift codes and others have iban numbers, others have account name and branch code. But they all use create recipient endpoint. Should you split the endpoint? Or use a flag in the validation logic? Or can you pass some kind of schema to the validation method, ie. The request should match a certain schema 100%
On one hand its a very neat implementation, but on the other there is a bit too much auto-wiring magic for my liking. Not sure I would go with this approach.
Can you explain how its "too much auto wiring magic" when you have to explicitly add WithRequestValidation to the endpoints?
Or are you talking about the auto registration of the validators using builder.Services.AddValidatorsInAssembly()? If it is this one, this is a very common thing that .NET projects do, register things by convention. If you are using Controllers, .NET has a builder.Services.AddControllers() method which will do the exact same thing, register all controllers to the DI container etc.
Just recently found your channel, i like your short, concise but informative videos, so here, have a subscribe
Thank you! Glad you like the videos