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

Callbacks are fired even though prevent_initial_call is set to True #9

Open
JohannesWiesner opened this issue Dec 22, 2021 · 1 comment

Comments

@JohannesWiesner
Copy link
Owner

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.

@JohannesWiesner
Copy link
Owner Author

Check this link, it might have something to do with this?:

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.

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

No branches or pull requests

1 participant