fix: maximum call stack size exceeded

[AuspeXeu]

Unfortunately, if the redis database has many entries, the current approach using recursion can run into a maximum call stack size exceeded exception.

[lzfxxx]

@jaredwray I've also encountered the same issue that's been addressed by this Pull Request #827 from @AuspeXeu. The problem with maximum call stack size exceeded exception due to recursion when the redis database has many entries is affecting my project as well. I kindly request that this Pull Request be considered for merging at the earliest possible convenience to resolve this common issue. I appreciate your work on this project and thank you in advance for your attention to this matter.

[jaredwray]

@AuspeXeu and @lzfxxx - thanks for the pull request. Can you get this updated as we just converted Redis to typescript. Can you do it based on that and make sure the tests run successfully so I can validate?

[AuspeXeu]

@jaredwray the tests fail due to a linting rule. Which does not seem to make sense for this particular case. Maybe we can deactivate it?

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (2919dff) 100.00% compared to head (db22e5c) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #827   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines         2465      2461    -4     
  Branches       245       245           
=========================================
- Hits          2465      2461    -4     

Impacted Files	Coverage Δ
packages/redis/src/index.ts	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[jaredwray]

@AuspeXeu and @lzfxxx this should be released next weekend with other updates. Thanks so much for the pull request!!!