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
This is because the user must edit the catches per entity in the current edit session for them to be skipped when picking catches.
Two possible solutions:
There are cases where users edit a trip and select more catches and want those fields to update, so perhaps we need to add new protobuf fields to track if the user explicitly set the catches per entity fields, so we can check on subsequent trip edits.
Another approach could be to ask the user if they want to override existing fields, which should apply to any field that is automatically updated after picking catches. Complication, though -- what if they want to override some fields, but not others -- it might be overkill to ask them which fields they want to change.
At the top of SaveTripPage, include a checkbox that explains that if checked, X fields will be calculated based on the catch selection.
Option 3 seems the best. If there's one or more fields they don't want overridden, they can uncheck the box for this trip.
The text was updated successfully, but these errors were encountered:
cohenadair
changed the title
Catches per entity still reset when editing a Trip
Trip data still reset after selecting catches while editing a trip
Jun 20, 2023
Reproduction Steps
Expected Result
Actual Result
This is because the user must edit the catches per entity in the current edit session for them to be skipped when picking catches.
Two possible solutions:
Option 3 seems the best. If there's one or more fields they don't want overridden, they can uncheck the box for this trip.
The text was updated successfully, but these errors were encountered: