Conversation
…ters. Only invoke setProps if it is defined, and fill in any missing keys for the view dictionary/object before rendering or computing a view.
|
I'm on https://dash-bio-test-pr-241.herokuapp.com/dash-bio/speck but I don't know how to test or experience the change: As a user, where can I supply a dictionary? What kind of dictionary? |
|
@mkcor Sorry about that! Basically, the dictionary values are set by the controls in the app (so, things like "atom size", "ambient occlusion", etc.) -- this doesn't really affect the app itself, since I do have callbacks that take the speck component as input ( dash-bio/tests/dashbio_demos/app_speck.py Line 260 in 4ea56b1 |
I noticed that the app had troubles which I will describe in the conversation
|
@shammamah ok, right, the end user never passes a dict (explicitly) as an input. Feel free to poke me when the PR is ready for final review! |
|
I can't approve as long as there are merge conflicts. I'm happy to resolve them if you let me work on your branch. Let me know. |
|
@mkcor This branch is still in progress! I'll ping you when it's ready :) |
|
This fix will become moot in the next dash release (cc @Marc-Andre-Rivet ) plotly/dash-renderer#126 |
|
Oh, okay! |
|
@mkcor We should get this merged in anyway, since it fixes the issue with |
|
Wait, I'm confused because this PR seems to contain these commits as well: https://github.com/plotly/dash-bio/pull/296/commits |
|
Closing this PR in light of the updates to |
About
Description of changes
Remove all "unprotected" calls to
setProps, which is only defined as a function if there is a callback in the Dash app that uses the component as input. Also ensure thatviewhas a full set of parameters at any given time (before, it would be restricted to the dictionary supplied by the user and there would be errors related to not being able to compute the rendering because of missing properties).Before merging