Multiple calls to onModelChange when element is getting created about declarativewidgets HOT 2 CLOSED

Starting to look into this one

from declarativewidgets.

For the function widget, we see 4 calls to _onModelChange: 2 from the parameters passed to the initial sync call (function_name and limit), 1 from an initial backend state update sent by the Jupyter Widget, and 1 from the backend signature update.

The first two are extra calls that should be silenced. We shouldn't filter the second two since they are triggered from state updates received from the backend.

I'll also look into preventing the initial backend state update in the python widgets, since the information that's sent (e.g. _view_name, version) isn't used by our widgets

from declarativewidgets.