Hi all,

our current solution for validation messages is the following:
-user enters bad value.
- this message comes up (e.g. for e-mail):
"component_id": Value is not a correct email-address."

if the developer uses *well named ids* all may be fine.
"emailValue": Value is not correct...

but on *silly ids* it is not clear to the users.
e.g. a: Value is not a correct emial....

However, if I changed the messages (on my box) to 
"[EMAIL PROTECTED]": Value is not a correct email-address.
this would be more sensible to the users.
What do you think?

But how should we handle *required*-messages?
the current (on my box) is still
"component_id": Value is required.

Any ideas?


Best regards
Mit freundlichen Gr��en
--
Matthias We�endorf
Aechterhoek 18
DE-48282 Emsdetten
Germany

Reply via email to