Allow getExtensionSettings to accept event as parameter #158
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.
Description
The function turbine.getExtensionSettings() can potentially be called from inside any condition/action exposed from an extension. Hence, the extension configuration should also be able to use the rule's synthetic event using %event%
Related Issue
#157
Motivation and Context
Passing the rule's synthetic event as parameter to turbine.getExtensionSettings() function call must be possible as this function internally calls replaceTokens() which replaces tokens with actual values. If in the extension configuration the user has used %event% as token, the turbine.getExtensionSettings() call from inside the action's/condition's module should be able to pass the event parameter it possess, so that the tokens are replaced with actual values coming from the event.
How Has This Been Tested?
Not tested
Screenshots (if appropriate):
Types of changes
Checklist: