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: add subbits/4 and subits/5 rule_engine functions #12652

Conversation

kjellwinblad
Copy link
Contributor

@kjellwinblad kjellwinblad commented Mar 5, 2024

The documentation for the family of subbits functions says that the fifth and sixth parameters are optional (since they only make sense when the forth parameter is 'integer'). However, before this commit subbits/4 and subbits/5 did not exist.

Fixes:
https://emqx.atlassian.net/browse/EMQX-11942
#12587

Fixes

Release version: v/e5.?

Summary

PR Checklist

Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:

  • Added tests for the changes
  • [] Added property-based tests for code which performs user input validation
  • Changed lines covered in coverage report
  • Change log has been added to changes/(ce|ee)/(feat|perf|fix|breaking)-<PR-id>.en.md files
  • For internal contributor: there is a jira ticket to track this change
  • [] Created PR to emqx-docs if documentation update is required, or link to a follow-up jira ticket (docs are already OK)
  • Schema changes are backward compatible

The documentation for the family of subbits functions says that the
fifth and sixth parameters are optional (since they only make sense when
the forth parameter is 'integer'). However, before this commit
`subbits/4` and `subbits/5` did not exist.

Fixes:
https://emqx.atlassian.net/browse/EMQX-11942
emqx#12587
thalesmg
thalesmg previously approved these changes Mar 5, 2024
changes/ee/fix-12652.en.md Outdated Show resolved Hide resolved
@kjellwinblad kjellwinblad merged commit 78d5f76 into emqx:master Mar 6, 2024
166 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants