Skip to content

Conversation

@Lidbetter
Copy link
Contributor

Changes proposed in this pull request:

  • Unbind default framework binding implementations of 'validator' (if wanting to use doctrine presence)
  • Tweak binding of PresenceVerifierProvider to account for the removal of the default 'validator' binding (if wanting to use doctrine presence)
  • Ensure the default implementation of ValidationServiceProvider has a db instance to use when checking to see if it should set the presence verifier (when using the default presence)

@Lidbetter
Copy link
Contributor Author

Fixes #202

@rgwsk65
Copy link

rgwsk65 commented Mar 21, 2017

Is there a chance of merge this PR?

* Register the validation factory.
*
* @return void
*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it necessary to redeclare this if we are extending ValidationServiceProvider ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the default implementation checks for different unrelated conditions before calling $validator->setPresenceVerifier

@patrickbrouwers patrickbrouwers merged commit 7d85114 into laravel-doctrine:1.3 Apr 24, 2017
@Lidbetter Lidbetter deleted the fix-validation-presence branch April 24, 2017 20:03
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