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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

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...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...