Closed TimPietrusky closed 5 years ago
This was fixed by correctly handling the way the properties are passed from the parent-component (fixture-detail-view) to it's children by connecting the parent to the store and listening to changes. Also we used hasChanged
to only re-render when the value actually changed, rather than on every state-change.
Issue description
When editing the properties using the
fixture-detail-view.js
view, the properties are not reset when switching to another fixture.Steps to reproduce
Versions