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
Currently, we calculate Mapshed data once for a project, and save it in its gis_data field. Each scenario can have modifications that affect parts of this object. This is currently done in multiple places. Here is sampling of some of them:
Refactor this so there is ONE canonical place where all the modifications for a scenario are combined into a single object, giving the canonical state for gis_data for that scenario.
There should be at most two places for such code to exist: once in the client and once on the server, but no more.
The text was updated successfully, but these errors were encountered:
Currently, we calculate Mapshed data once for a project, and save it in its
gis_data
field. Each scenario can have modifications that affect parts of this object. This is currently done in multiple places. Here is sampling of some of them:model-my-watershed/src/mmw/js/src/modeling/models.js
Lines 1579 to 1637 in e966cc9
model-my-watershed/src/mmw/js/src/modeling/models.js
Lines 1639 to 1662 in e966cc9
model-my-watershed/src/mmw/js/src/modeling/models.js
Lines 1664 to 1705 in e966cc9
model-my-watershed/src/mmw/js/src/modeling/gwlfeModificationConfig.js
Lines 100 to 125 in e966cc9
model-my-watershed/src/mmw/apps/modeling/calcs.py
Lines 261 to 288 in e966cc9
with their many usages.
Refactor this so there is ONE canonical place where all the modifications for a scenario are combined into a single object, giving the canonical state for
gis_data
for that scenario.There should be at most two places for such code to exist: once in the client and once on the server, but no more.
The text was updated successfully, but these errors were encountered: