Renaming function names for consistency about validator.js

If API changes aren't made due to the fear to break code libraries won't get better.

The usual way would be to just have an alias for the old one and put a deprecation warning.

Imo the most annoying things are not the changes, it's that code breaks and you don't even know why. Deprecation warnings will make the transition smooth. Just like how Ryan did with the sys -> util module in Node.js.

Would you merge my pull request if I implemented the above suggestion with deprecation warnings? I would want to contribute to make this library better.

[chriso]

I agree it reads better but I'm wary of changing an API that's a year old. Renaming functions at this stage would break a lot of code

[chriso]

I'm still wary about doing this.

I completely agree with what you're saying with regards to changing API's and deprecating methods in the name of moving forward, but I think that introducing deprecated warnings for some minor naming inconsistencies is the wrong way to go considering that Javascript APIs are inherently open and that users can fix these inconsistencies with their own mixins.

Another thing is that this library is in use client-side as well as server-side so deprecated warnings are not only a pain for existing code, they don't really work client-side.