Project Wonder validation-localization is a real time saver.
-No more calls to WORessourceManager and its infamous 5 arguments =20
-A unified design for model based / custom validation
-Less localized strings thanks to templates.
I no longer find myself hesitating to mark a property "not null" in =20
my model, thinking "I will have to deal with it in my code".
But I only partially understand how templates work.
What I have been able to acheive so far is to generate a message like
"Veuillez choisir un(e) <b>bonne r=E9ponse<b>"
By writing a template entry like:
NullPropertyException =3D "Veuillez choisir un(e) =20
"correctAnswer" =3D "bonne r=E9ponse";
I don't understand how I could have a different message for the same =20
property key, but for different entities.
That is, for entity "SliderQuestion", correctAnswer should map to =20
"expected number", and for entity "TextEntryQuestion" correctAnswer =20
should map to "expected answer".
Can this be acheived by means of templates?
Get latest updates about Open Source Projects, Conferences and News.