Skip to content

Conversation

@Avital-Fine
Copy link
Contributor

@Avital-Fine Avital-Fine commented Mar 16, 2022

Description

CONFIG SET
Closes #1936


Checklist

  • Does npm test pass with this change (including linting)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
@codecov-commenter
Copy link

codecov-commenter commented Mar 16, 2022

Codecov Report

Merging #2042 (4576b5e) into master (be51abe) will not change coverage.
The diff coverage is n/a.

@@ Coverage Diff @@ ## master #2042 +/- ## ======================================= Coverage 94.83% 94.83% ======================================= Files 360 360 Lines 3366 3366 Branches 411 411 ======================================= Hits 3192 3192 Misses 89 89 Partials 85 85 

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be51abe...4576b5e. Read the comment docs.

const args = ['CONFIG', 'SET', parameter, value];

if (mulitipleParams) {
mulitipleParams.forEach(pair => args.push(pair[0], pair[1]));
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we destructure for clarity?

Suggested change
mulitipleParams.forEach(pair => args.push(pair[0], pair[1]));
mulitipleParams.forEach(([parameter, value]) => args.push(parameter, value));
@leibale leibale merged commit c5c2bf9 into master Mar 20, 2022
@leibale leibale deleted the CONGIF_SET_NEW_FEATURE branch March 20, 2022 17:40
florian-schunk pushed a commit to florian-schunk/node-redis that referenced this pull request Jun 18, 2025
* support multiple parametrs on CONFIG SET * clean code Co-authored-by: leibale <leibale1998@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants