Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: hmset, mset should accept value = 0 #2531

Merged
merged 6 commits into from
May 22, 2024
Merged

Conversation

Juiced66
Copy link
Contributor

What does this PR do ?

  • fix bugs in MS controllet :
    • hmset should accept value: 0
    • mset should accept value: 0

How should this be manually tested?

npm run test:unit

boyscoot

  • fix typo

@Juiced66 Juiced66 changed the title Fix/hset and hmset 0 value fix: hmset, mset should accept value = 0 May 17, 2024
@Juiced66 Juiced66 self-assigned this May 17, 2024
Copy link

sonarcloud bot commented May 17, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@Juiced66 Juiced66 merged commit 8099cc2 into 2-dev May 22, 2024
33 checks passed
@Juiced66 Juiced66 deleted the fix/hset-and-hmset-0-value branch May 22, 2024 06:50
@kuzzle
Copy link
Contributor

kuzzle commented Jun 3, 2024

🎉 This PR is included in version 2.30.1-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

None yet

4 participants