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
The code block below facilitates populating annual cover events with observation (cover) data. While this works as intended such that clicking on a button to populate a cover event calls another module that facilitates adding the actual cover data; clicking on another cover event removes the module associated with the previous event and raises a new module of cover data associated with the newly selected cover event. There are two problems. First, the cover event id to populate is always cover_event_0 in the DOM. This is a problem because it is not clear why. More importantly, it makes it unclear how to remove the cover composition module associated with the cover event from another part of the application. Here is an example: click to populate a particular cover event, then click to edit a different cover event. In that scenario, the module to populate the first cover even remains visible even though the user elected to edit the details of a different cover event. This is not necessarily a serious concern or impediment to the workflow but best would be to have the module to populate the cover event removed when any action on another cover event is selected just to avoid potential confusion.
The code block below facilitates populating annual cover events with observation (cover) data. While this works as intended such that clicking on a button to populate a cover event calls another module that facilitates adding the actual cover data; clicking on another cover event removes the module associated with the previous event and raises a new module of cover data associated with the newly selected cover event. There are two problems. First, the cover event id to populate is always
cover_event_0
in the DOM. This is a problem because it is not clear why. More importantly, it makes it unclear how to remove the cover composition module associated with the cover event from another part of the application. Here is an example: click to populate a particular cover event, then click to edit a different cover event. In that scenario, the module to populate the first cover even remains visible even though the user elected to edit the details of a different cover event. This is not necessarily a serious concern or impediment to the workflow but best would be to have the module to populate the cover event removed when any action on another cover event is selected just to avoid potential confusion.The text was updated successfully, but these errors were encountered: