You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all callbacks are fired, even though I set prevent_initial_call=True. This does not affect any functionality off the app but should be fixed.
The text was updated successfully, but these errors were encountered:
However, the above behavior only applies if both the callback output and input are present in the app layout upon initial load of the application.
It is important to note that prevent_initial_call will not prevent a callback from firing in the case where the callback's input is inserted nto the layout as the result of another callback after the app initially loads unless the output is inserted alongside that input!
In other words, if the output of the callback is already present in the app layout before its input is inserted into the layout, prevent_initial_call will not prevent its execution when the input is first inserted into the layout.
Currently, all callbacks are fired, even though I set
prevent_initial_call=True
. This does not affect any functionality off the app but should be fixed.The text was updated successfully, but these errors were encountered: