Skip to content

Library evolution #79

Description

@artemeff

I think this library is done, it has non-idiomatic API with just a few really useful functions, like scripts execution and defredis macro (thank you guys for implementation 🤘).

This library can be more valuable, we need to stop being just a wrapper around eredis and give something better to developers.

Right now I’m writing a module that makes Elixir functions from commands.json file. I’m already done with required and optional arguments, commands (like COUNT and STORE in GEORADIUS), enums (like WITHCOORD, WITHDIST in GEORADIUS) and many other little things. Every generated function has typespecs and documentation. As a result, I want to make this library, like when you don’t want to look at the documentation at all (on redis.io, I mean), just hover at the function in your modern editor :)

redis

The second most important change I want to make — rename the library to Redis. Old Exredis code will be in a separate branch and the new library will be published under the new name. With this change, we can test new functionality much faster and give a second wind to it.

Also, I want to make adapters for popular Redis clients (Redix and eredis), to make this library more flexible (but it's in question).

Summarizing:

  • generate Elixir functions from Redis commands.json with docs and typespecs;
  • rename Exredis to Redis;
  • adapters for Redix and eredis?

What do you think?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions