feat(functions): Implement COUNT function#587
Merged
rabbitstack merged 1 commit intomasterfrom Feb 1, 2026
Merged
Conversation
a160ff5 to
5784108
Compare
The count function counts the number of items in the slice or substrings in the string that is matching a wildcard pattern.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of this PR / why it is needed?
The
COUNTfunction counts the number of items in the slice or substrings in the string that match a wildcard pattern. Thefunction receives the string/slice, the wildcard pattern, and optionally the parameter that indicates if the item count is performed
in a case-insensitive way (default true).
What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area rule-engine
/area filters
Special notes for the reviewer
Does this PR introduce a user-facing change?
Update the docs to reflect that the new function exists in the rule language idiom.