rx.call_script: a real EventHandler to execute arbitrary javascript #1860
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 existing
rx.client_side
cannot be chained from a backendEventHandler
since it is aBaseVar
.This new
rx.call_script
"server-triggered" event can be used to fire arbitrary js code on the page after performing backend processing without user intervention...and it can also be used in an event trigger (like on_click).The main difference with
rx.client_side
is that we cannot access all args coming from the js trigger call, since those are handled by theget_event_triggers
API. But now thatget_event_triggers
allows arbitrary arg mapping, this limitation does not matter as much.Inspired by and Supersedes #1357
Fix #1346
Sample Code
(make sure to (re)run
reflex init
, since this contains changes tostate.js
)