Implement rule chaining support for @RuleName references and success events #680
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.
This PR implements rule chaining functionality that allows rules to reference the results of previously executed rules using
@RuleName
syntax and success event names.Problem
Users were unable to chain rules together where subsequent rules depend on the results of previous rules. The specific issue was that expressions like
@EvaluationExpression && metrics.cost_limit >= -1
would fail with "Unknown identifier '@EvaluationExpression'" errors.Solution
Modified the rule execution flow to:
@RuleName
and success event names)@RuleName
withRuleName
before compilationExample Usage
Key Features
@RuleName
references: Evaluate to the boolean result of the referenced ruleEvaluationExpressionPassed
)EnableScopedParams = true
Testing
Added comprehensive test coverage including:
All existing tests continue to pass, ensuring no regressions.
Fixes #679.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.