Rodrigo Rosenfeld Rosas

Sorry, I didn't understand. How much dryier can this be? All validators just call the message method from Validator (from which them all inherit from). That met...

I have dryied the code. The part I have changed in all validators were necessary because it was not modular, so I couldn't change just one place. See an example...

Here is a new patch (still lacking documentation and tests) using your suggested approach.

Should I post to rails core list again asking for help on documentati...

Just small improvements, following best practices for HTML writing:

b -> strong
p -> div for non-paragraphs

And added a meta for defining charset to utf-8, as i...

You're right. When I tested subclassing String, I probably missed the message parameter in initialize.

But it is still a hack in the sense that unexpected thing...

Valim, I have first tried the list, as you can see in the link I've posted in my first comment, but I didn't get any help there.

I had already discussed the iss...

There is no documentation nor test files in the patch because I need some help about how to write them.

I've asked for instructions in the topic below but got n...

Follows a patch to add a full_message option to validations.

Currently Rails don't allow full control over validation messages without making use of I18n and ev...

I've just realized this mistake in the last message:

validates_presence_of :login, :message => 'You must specify a user name.'

Of course, I meant:

validates_pre...

I'm afraid I was not clear in my last message. What I meant for often, is that :full_message would be rarely used inside a project, but that projects will often...