Implemented PHPUnit, Comply to PSR4, Allow custom \Redis objects #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I did a bunch of commits that i needed for this to run against my system.
You might want to cherry-pick what makes sense.
RedLock
class into a vender namespaceRedLock
(might break backwards compatibility for people usingdev-master
to install package.redis-server
instances used in testing.\Redis
object instead of the[$host, $port, $timeout]
array. (if user is already dealing with a connection, why open a new one)\Redis
objects can now be passed, the$token
used to unlock the lock must be serialized with the\Redis
objects serializer. This is important if the user is using something than the default serializer (like igbinary).