-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Impossible to set Redis config #22
Comments
Submitted a pull request. |
Hey, sorry about that actually. I completely forgot about the Redis options even though I knew it was a problem (I always had my redis stuffs on default so I forgot about it being an issue). I'll check out your PR. |
No problem ! I can also help you to write the RedisCache docs if necessary ;-) |
If you want to, I'd appreciate it. If anything, I'll write it by the end of the day. |
@Ilshidur To run the tests, also set KEY_TO_RATE_LIMIT to your dev key (there's a test that mocks the 429 retries until successful). I'll add this to docs as well (Contributing?). edit: I also have to update this test now that the rate limit has changed. published to 2.0.74 Updated Wiki Docs to show current Redis options (https://github.com/ChauTNguyen/kindred-api/wiki/Caching#redis-cache-example) and also updated the README to have a small configurable Redis example in the README Introduction section. |
Awesome ! Closing the issue, since you solved it :) |
First of all, I really like your lib. Keep up the good work !
I'm facing issues when trying to set the Redis cache options.
I got this :
The problem is that it is impossible to set the Redis config I want. They always get overridden by your default config. See here. Your code behaves this way : whatever the user gives, the default options are overriding it.
The way to fix this is to change the line to this :
The second problem is that the Wiki needs more docs about the RedisCache options. I had to dig in the lib code.
If you don't have the time to fix this, I can send you a PR with the fixed code :)
The text was updated successfully, but these errors were encountered: