Baptiste Clavié
Baptiste Clavié
For some reasons, on the travis, I have some failure, and I don't really understand why as it's nothing I touched ? Especially as the PR I opened before (#264)...
I also thought about preventing the `notNot` calls. Either by preventing a `not()` call or inverting it (`notNotBlank` becomes `blank`). I'd rather add the first check though I'll try to...
Note that I also thought about just catching the exception and return true, but as you said, the hard bit is creating the alternate message...
After a "quick" look, I don't think it really is easily manageable to add a `not` switch on the `__callStatic`, for the following reasons... 1. As you already mentionned it,...
Rebased onto upstream/master. Ping @rquadling (Still looking for suggestions on how to handle things properly)
(Failures unrelated)
I removed the `@deprecated`. I thought that the given message (using `empty` instead) would do the trick, unless you'd like to add a `trigger_error` with it ? Not sure what...
Rebased and updated from upstream/master.
Had my eyes on this a short while ago, not sure if it is pertinent to have a graphql step to be honest, as a graphql reequest can be sent...
Tools to maybe migrate to ; - https://github.com/wbthomason/packer.nvim instead of current vim packer