The Validot project comes with comprehensive documentation, excellent for looking up how certain features work. On the other hand, documentations don’t always serve as great tutorials or walkthrough guides, which in Validot is very much the case. This blog post aspires to answer this problem. Following the real-life use case, we’ll proceed step-by-step with creating a fully-featured specification using Validot’s advanced fluent-driven interface.

The story behind creating my first general use, performance-first library.

REST API Data validation using FluentValidation and Pipeline Pattern. Implementing Problem Details standard.

FluentValidation, czyli jak zapewnić czytelną implementacje reguł walidacji po za klasą modelu.

About two months ago I worked on the microservice for my company’s new product. The whole thing was based on the CQRS pattern which is basically about splitting the application into reads (queries) and writes (commands). I came to the point when I wanted to validate a command object received from RabbitMQ. Without thinking, I started coding another if statements which after a while became my „domain logic”. I’m not going to present the example code because I’m ...

To be honest, I thought that my previous post would be the last in the CQRS/ES series, but I forgot to discuss one more thing related to that topic. Many developers don’t know how we should handle the following scenario in our systems:   „During the creation of user’s new account I would like to verify rather a username is unique in the whole database. Should I use Event Store or Read Database for a query? Where should I check that?”   Seriously, that question is one of the most popular topics connected ...

In this post I will try to introduce the concept of validation using the Chain of Responsibility pattern (CoR), which I use successfull for years

It is a common practice to validate function arguments before running actual code. Usually validation looks like that: public void Update(Car entity) { if(entity ==null) throw new ArgumentNullException("entity"); } There is nothing wrong with this code, however we have to repeat this piece of code in every function. Of course we could create some helper class for argument validation and call approperiate validation function before launching...

No to embargo na informacje na temat SharePoint 2010 zostało zdjęte :) pora więc rozpocząć posty na jego temat :) W netcie znajdziecie już dużo screenów, więc nie będę się zajmował stroną wizualną a jedynie programistyczną. Pierwszym tematem jest nowa funkcjonalność walidacji danych na formularzu. Zaraz po wejściu na ustawienia listy widać nowy element Validation Settings: