-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support providing and accessing context in rules #133
Merged
Merged
Conversation
This file contains 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
jimtng
force-pushed
the
rule-context
branch
3 times, most recently
from
September 2, 2023 01:39
eed6097
to
615e4d9
Compare
jimtng
commented
Sep 2, 2023
ccutrer
reviewed
Sep 7, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add a spec that verifies a local variable "hides" any incoming context?:
command = ON
rule do
received_command Switch1
run do
expect(command).to be ON
ned
end
Switch1.off
Working on adding the spec |
Signed-off-by: Jimmy Tanagra <[email protected]>
specs added |
ccutrer
pushed a commit
that referenced
this pull request
Sep 8, 2023
…ngGroup (#123)" (#138) This reverts commit 8cb45f6. Reasons: * Unable to access toplevel UI local variables to get to `triggeringGroup`, so #123 created an inconsistency where event.group is only available on file-based rules * File-based rules now has access to top level context so it can use `triggeringGroup` just like UI rules, since #133 Signed-off-by: Jimmy Tanagra <[email protected]>
ccutrer
approved these changes
Sep 8, 2023
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.
No description provided.