Why can an output only have a single callback function?

[caiyij]

I agree. It would be great if we can have more than one callback for an output. For buttons especially it’s hard to use two buttons as inputs in one function, since it’s hard to tell which one is clicked.
But instead of using n_clicks as input, maybe you can try the click event.
The code from this post:

Manange "enter" event on button

Thank you @nedned. However, I want to avoid the user to have to use the mouse (or some “tab” dance) to push the data in the Input to python (my workaround today is indeed having the button). btw, with the constraint of allowing only one callback per Output, I need to consolidate all events/inputs possibly changing an output in a single callback. But then, to identify what button (when there are multiple buttons) has been clicks in the callback is painful. Either the callback is triggered throu…

@app.callback(Output('target', 'children'), [], [State('input', 'value')], 
              [Event('submit', 'click'), Event('other-action', 'click')])

It’s using two click event to trigger the function. So you can probably modify your code to use just one function for the output then you won’t be needing more than a single callback.