✨ Adding a Scope to the running of the rule engine #723
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
Signed-off-by: Juan Manuel Leflet Estrada <[email protected]>
…he running engine and the caller of run rules Signed-off-by: Shawn Hurley <[email protected]>
shawn-hurley
force-pushed
the
feature/add-included-paths-to-running-rules-engine
branch
from
dbd47c4
to
acd5eb4
Compare
Signed-off-by: Shawn Hurley <[email protected]>
shawn-hurley
force-pushed
the
feature/add-included-paths-to-running-rules-engine
branch
from
6608f40
to
a4a8f6f
Compare
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.
The scope will allow for users to call the engine directly will be able to add information to the condition context. Providers are still responsible for restricting based on that condition context.
Working off of @jmle awesome work to get the file paths respected in providers