Skip to content
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

Allow setting a different invocation function for EventChain #4160

Merged
merged 1 commit into from
Oct 11, 2024

Conversation

masenf
Copy link
Collaborator

@masenf masenf commented Oct 11, 2024

In rx.call_script scenario, the EventChain must call queueEvents and processEvent instead of addEvents, because the former are in scope in the call_script eval environment where addEvents is not.

This is an escape hatch for certain wrapping scenarios.

In rx.call_script scenario, the EventChain must call `queueEvents` and
`processEvent` instead of `addEvents`, because the former are in scope in the
call_script eval environment where `addEvents` is not.

This is an escape hatch for certain wrapping scenarios.
@masenf masenf merged commit a2862bd into main Oct 11, 2024
31 checks passed
@masenf masenf deleted the masenf/event-chain-invocation branch October 11, 2024 23:49
Kastier1 pushed a commit that referenced this pull request Oct 23, 2024
In rx.call_script scenario, the EventChain must call `queueEvents` and
`processEvent` instead of `addEvents`, because the former are in scope in the
call_script eval environment where `addEvents` is not.

This is an escape hatch for certain wrapping scenarios.
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.

2 participants