You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2022. It is now read-only.
This isn't a huge deal since we'll be completely replacing KO with elm (or react/redux depending on how that experiment works out) but it appears the elm bindings are somehow impacting the way the KO mapping plugin manages its child bindings (analyses + analysis outputs).
The buggy use case for this is running analysis scripts or deleting analysis outputs not updating properly the view. You can see what it should look like on the master branch, and see what is currently happening on the elm branch.
As it stands I won't be deploying the elm branch on production unless this gets fixed, since script running is more central to the project than an improved data group metadata management interface and I don't want to have to refresh the browser constantly during the live demo.
The text was updated successfully, but these errors were encountered:
When I get rid of the Elm embed in the metadata tab and the include for the elm code deleting analysis outputs still does not update the view. Outputs are also not added once an analysis is completed.
When I get rid of the Elm embed in the metadata tab and the include for
the elm code deleting analysis outputs still does not update the view.
Outputs are also not added once an analysis is completed.
This isn't a huge deal since we'll be completely replacing KO with elm (or react/redux depending on how that experiment works out) but it appears the elm bindings are somehow impacting the way the KO mapping plugin manages its child bindings (analyses + analysis outputs).
The buggy use case for this is running analysis scripts or deleting analysis outputs not updating properly the view. You can see what it should look like on the master branch, and see what is currently happening on the elm branch.
As it stands I won't be deploying the elm branch on production unless this gets fixed, since script running is more central to the project than an improved data group metadata management interface and I don't want to have to refresh the browser constantly during the live demo.
The text was updated successfully, but these errors were encountered: