Using a single callback function triggered on dcc.Location gets hairy when there are multiple actions and each action affects a different set of outputs.
I thought @server.route might help:
server = app.server @server.route("/action/<string:target>/<int:value>/") def handleAction(target,value) : ...
Some of the actions don’t affect outputs, so this works great, but there doesn’t seem to be any way to trigger a callback programatically for the ones that do affect outputs.
I can’t use the @server.route approach for the ones that only change state on the server side, with a dcc.Location callback for the ones that affect outputs, because the dcc.Location callback catches all of the events and the server.route endpoint never fires.
It would be especially awesome if I could use @server.route and somehow trigger a callback when needed.