Skip to content

docs(event-gateway): state that filters have no regex operator - #31

Open
leggetter wants to merge 1 commit into
mainfrom
docs/filters-no-regex
Open

leggetter wants to merge 1 commit into
mainfrom
docs/filters-no-regex

Conversation

@leggetter

Copy link
Copy Markdown
Collaborator

connection-rules.md lists the filter operators but never says regex is not one of them. An agent that searches the skill for "regex", as one did in hookdeck/evals run 41430462176, finds nothing and falls back on its own belief. In another run an agent with no skill invented a $regex operator outright (hookdeck/evals#100).

This states the boundary on the operator line. It also adds $ref, which the filters docs list and the skill omitted, and names the logical operators already listed above it, so the line is the full set the docs give.

Measured in hookdeck/evals#100 once the benchmark's skills pin moves.

🤖 Generated with Claude Code

connection-rules.md listed the filter operators but never said regex is not
one of them. An agent that searched the skill for "regex" found nothing and
fell back on its own belief (hookdeck/evals run 41430462176). Another agent,
with no skill, invented a $regex operator outright (hookdeck/evals#100).

Name the full operator set on one line, adding $ref, which the filters docs
list and the skill omitted. Say plainly that there is no regex operator, and
point pattern matching at transformations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant