Skip to main content

Caz in care IValidatableObject.Validate nu este apelat

Daca in aplicatia voastra MVC in loc de Enterprise library pentru validare o sa fiti surprinsi ca exista cazuri cand metoda pentru validare nu este apelata asa cum v-ati astepta.
Folosind atributele HasSelfValidate si SelfValidate, putem sa validam un obiect. Atributul HasSelfValidate ne spune daca obiectul curent are un mecanism propiu de validare. Metoda care face validarea in interiorul obiectului nostru trebuie sa aibe atributul SelfValidation si urmatorul antet:
void numeMetoda( ValidationResults validationResults )
In cazul in care obiectul nu este valid putem sa adaugam pe validationResults mesajul dorit impreuna cu alte informatii precum: nume propietate si referinta la obiectul care nu este valid.
[HasSelfValidate]
public class Person
{
public int Age { get; set; }

public int Name { get; set; }

[SelfValidation]
public void Validate(ValidationResults validationResults)
{
if( Age < 0 )
{
validationResults.AddResult(new ValidationResult("Varsta este negativa", this, "Age", null,null);
}
if( string.IsNullOrEmpty( Name ) )
{
validationResults.AddResult(new ValidationResult("Numele nu este valid", this, "Name", null,null);
}
}
}
In cazul unei aplicatii MVC clasa noastra o sa aibe forma urmatoare:
public class Person : IValidatableObject
{
[Required]
public int Age { get; set; }

[Required]
public int Name { get; set; }

public IEnumerable[ValidationResult] Validate(ValidationContext validationContext)
{
if( Age < 0 )
{
yield return new ValidationResult("Varsta este negativa", new [] { "Age" });
}
if( string.IsNullOrEmpty( Name ) )
{
yield return new ValidationResult("Numele nu este valid", new[] { "Name"});
}
}
}
Mecanismul este exact la fel ca si cel cu atribute, doar ca implementam o interfata. Am putea spune ca cele doua implementări au același comportament pentru orice caz. Dar din pacate nu este adevarat. Pentru a doua implementare o sa apara cazuri cand metoda noastra de validare nu se apelează.
Daca Age sau Name nu este completat o observam ca metoda Validate nu este apelata. Totul apare din cauza atributului Required, care verifica daca s-a introdus o valoarea pentru propietatea marcata, iar daca valoarea nu a fost introdusa nu o sa apeleze metoda Validate. Acest comportament apare din cauza ca prima data se face validarea propietatiilor in functie de atirbutele cu care sunt decorate, iar doar apoi daca validarea a fost cu succes se apeleaza metoda noastra
Acest caz nu ar trebuii sa ne deranjeze in general. Dar trebe sa il avem in vedere pentru anumite cazuri. De exemplu faca avem o pagina unde un user se inregistreaza si acesta nu introduce numele, dar introduce parola, poate am dorii sa apara un mesaj in care sa ii se spuna ca parola nu este destul de sigura sau ceva asemanator.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...