-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
[Bug] Components as props in dmc.Notification
not working correctly
#235
Comments
Hi @AnnMarieW, you are writing a callback on a component passed as a property. Are callbacks supposed to work on them now? |
Hello @snehilvj, The callback is to demonstrate the issue with the setProps and trying to increase the n_clicks value of the individual component. I'm not sure if notifications are setup this way, I think if this was to work, would the notification need to be rerendered? The component triggers a rerender in itself, but because the prop value doesn't increase, a new test for n_clicks in the clipboard fails. |
Hi @snehilvj If you take a look at the examples in the issue in the Dash repo, you can see what was originally reported is that the It looked like it was an issue with |
dmc.Notification
not working correctlydmc.Notification
not working correctly
I haven't been able to figure out the root cause of this bug. I suspect it might have something to do with how the refs are handled and it might be an issue in the Dash library. If anyone has any ideas, I could use the help because this one has me stumped. |
This issue was initially reported in the Dash GitHub plotly/dash#2830, but it seems to be an issue only with the
dmc.Notification
component.When using components as props, the component's onClick handler no longer works correctly. Note that in this example if you click on the dmc.Button inside the
dmc.Notification
multiple times then_clicks
remains at 1.The text was updated successfully, but these errors were encountered: