Behavior observed in dash==1.2.0 but has probably been present since multi-output support was added, shortly after loading_state, both in dash==0.39.0.
The assumption is that all request strings are of the form id.prop but multi-output is of form ..id1.prop1...id1.prop2...id2.prop3.., resulting in '' component and prop name.
Expected behavior would be for prop_name to be an array of strings with the affected props if multiple values are found.
Behavior observed in
dash==1.2.0
but has probably been present since multi-output support was added, shortly after loading_state, both indash==0.39.0
.Problematic handling of multi-output is here: https://github.com/plotly/dash/blob/master/dash-renderer/src/TreeContainer.js#L313
The assumption is that all request strings are of the form
id.prop
but multi-output is of form..id1.prop1...id1.prop2...id2.prop3..
, resulting in''
component and prop name.Expected behavior would be for
prop_name
to be an array of strings with the affected props if multiple values are found.Test app - observed while reviewing / testing https://github.com/plotly/dash-table/pull/484 (the test case is essentially described here: https://github.com/plotly/dash-table/pull/484/files#r319109146)