.NET folks, don't miss J. Tower's two #techbash sessions this fall!
Join us at Kalahari Resort in the #poconos Nov 7-10. Learn more: https://techbash.com
#dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
#techbash #poconos #dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
@tpetrina Thanks for pointing out that usecase, that's one advantage I thought of as well. I kinda had an argument with someone who uses records now for everything and that I find problematic. E.g. you can't inherit from libs like #FluentValidation with records.
For the usecase you blogged about I think it's nice, but with .Net8 I would still prefer classes with primary constructors I guess.
I just learned that #FluentValidation added a "ChildRules" method, which allows you to validate nested objects without any additional validators.
That's helpful when you have a #dotnet object graph that is not used outside the root. Sweet.
My first try using chatGTP to create a Xamarin.Forms login page with #ReactiveUI, #Fody #Refit #FluentValidation (Spanish though). Amazing results IMO.
https://www.youtube.com/watch?v=LS7Ot3GLfjc
#reactiveui #fody #refit #fluentvalidation