Update: version 1.16 has been released since this was posted. Dash v1.11.0 is a minor release introducing the new Pattern-Matching Callbacks feature and providing multiple bug fixes improving the performance, robustness and behavior of Dash callbacks. Official Changelog Dash v1.11.0 Highlights …

We are very excited about Pattern-Matching callbacks! This is one of the biggest features & deepest overhauls to Dash’s core architecture that we’ve made since we originally released the framework in 2017. In August 2017, one month after we released Dash, we opened up a forum topic about one of the…

Amazing news! This is by far the Dash release that i have been looking forward to the most :smiley:

This is amazing news. Thank you. In addition, I have one question about app.config.suppress_callback_exceptions. So I have a multi-page application, I have a callback function1 to generate a barchart with id b1. Then I have a callback function2 that use id b1 as input to get its clickData value. W…

Hi @meg - sorry about this, it does look like the behavior around this case changed, though we’re trying to figure out if it should actually be considered a bug. If I take the code you posted and run it in dash 1.10 it looks like it’s OK, no error shows up in the on-page devtools. But there actually…

I am also seeing this issue in one of my full apps. The weird thing is that i have numerous callbacks linked to components that do do not exist, but only a few of them are throwing the error. For now, i have used wildcards to silence the error for these components, [image] Referenc…

After updating to 1.11.0, i have also started seeing the following warning in the js console, react-dom@16.v1_3_0m1586552074.13.0.js:82 Warning: Cannot update a component from inside the function body of a different component. The app seems to work fine though.

@Emil same question I asked @meg - if you run this app with v1.10, do you see any errors in the JS console? My understanding is these callbacks would always have tried to fire, and it was always supposed to be an error to have partially-defined callbacks. But as the example Meg posted shows, we were…

Cannot update a component from inside the function body of a different component. I saw that at some point as well but haven’t tracked it down. Do you know if this error started showing up in 1.11 or if it was already there in v1.10? I was going to guess that it was introduced by the React upgrad…

Hi all, I have a similar problem as @meg and it’s clearly a 1.11.0 issue (doesn’t appear in 1.10.0). It appears within a callback that is fired on instantiating the app. It dynamically creates some components, registers some callbacks and then returns the components in the layout (as a html.DIV’s…

Hi @alexcjohnson . Thanks for the reply. When I use 1.10 in my full app, I didn’t see ReferenceError. [image] I believe your suggestions on the work around should solve this problem. Regardless of whether the error is new, is this going to be an open issue and plan to resolve in future releases? T…

📣 Dash v1.11.0 Release - Introducing Pattern-Matching Callbacks - #3 by chriddyp - Dash Python

Topic		Replies	Views	Activity
:mega: Pattern Matching Callbacks & Dynamic Callback Support - In Development, Looking for Feedback Dash Python show-and-tell , announcements	18	9010	April 10, 2020
Dynamic Controls and Dynamic Output Components Dash Python	11	47573	April 10, 2020
Output not shown correctly with pattern-matching callbacks Dash Python	3	1523	June 18, 2022
Duplicate Callback Outputs - Solution & API Discussion Dash Python	22	11148	March 16, 2023
Is suppress_callback_exceptions no longer supported in Dash v1.11.0 Dash Python	3	4877	April 18, 2020