Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX for #4417: Ensuring ->removeValidation() is defined on instances of Validator. #4418

Conversation

patricknelson
Copy link
Contributor

Quick fix for #4417. Went ahead and based this on 3.1.

Might cause some issues for people who haven't defined this method and happen to also not actually need it, even though they're still technically at risk of a fatal error if that method is called in the future, should they ever have a validated form which is also not editable.

@dhensby
Copy link
Contributor

dhensby commented Jul 22, 2015

This can't go in 3.1 as it is going to cause errors for anyone who has extended the base Validator but hasn't implemented that function.

I think the fix for 3.1 should be to check the method exists on validator before calling it. Probably the same for 3.

Then master can have this change

@tractorcow tractorcow closed this Jul 30, 2015
@tractorcow
Copy link
Contributor

Please re-open a new PR for this branch on master, ta!

@dhensby
Copy link
Contributor

dhensby commented Aug 20, 2015

Can a core member her this in master if we don't see this opened by the original author?

@patricknelson
Copy link
Contributor Author

Hello visitors from the future! New PR is here: #4542

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants