Changelog History
Page 5
-
v0.3.0 Changes
๐ฅ Breaking changes
Change the behaviour for an empty list of command passed to
Redix.pipeline/2
(Redix.pipeline(conn, [])
), which now raises aRedix.ConnectionError
complaining about the empty command. Before this release, the behaviour was just a connection timeout.Change the behaviour of empty commands passed to
Redix.command/2
orRedix.pipeline/2
(for example,Redix.command(conn, [])
orRedix.pipeline(conn, [["PING"], []])
); empty commands now return{:error, :empty_command}
. The previous behaviour was just a connection timeout.Remove
Redix.start_link/1
in favour of justRedix.start_link/2
: now Redis options are separated from the connection options. Redis options can be passed as a Redis URI as well.
๐ Bug fixes and improvements
- Change the error messages for most of the
Redix.ConnectionError
exceptions from simple atoms to more meaningful messages.
-
v0.2.1 Changes
- Fix a bug with single-element lists, that were parsed as single elements (and not lists with a single element in them) by
Redix.Protocol.parse_multi/2
. See whatyouhide/redix#11.
- Fix a bug with single-element lists, that were parsed as single elements (and not lists with a single element in them) by
-
v0.2.0 Changes
Rename
Redix.NetworkError
toRedix.ConnectionError
(as it's more generic and more flexible).Add support for PubSub. The following functions have been added to the
Redix
module:Redix.subscribe/4
Redix.subscribe!/4
Redix.psubscribe/4
Redix.psubscribe!/4
Redix.unsubscribe/4
Redix.unsubscribe!/4
Redix.punsubscribe/4
Redix.punsubscribe!/4
Redix.pubsub?/2
-
v0.1.0 Changes
๐ Initial release.