Closed bpintel closed 6 months ago
These are great changes! Did catch one error when inputting to flow measure on trap operations And noticed that trap and catch are being submitted more times than on dev
These are great changes! Did catch one error when inputting to flow measure on trap operations And noticed that trap and catch are being submitted more times than on dev
Thanks Hunter, I just added an extra condition to the edge case in useFlowMeasureCalculationBool
What number of submissions are you getting on dev? I have:
Typing that out I just noticed the number of submissions is incrementing by 1. This might be a clue to what is causing this.
These are great changes! Did catch one error when inputting to flow measure on trap operations And noticed that trap and catch are being submitted more times than on dev
Thanks Hunter, I just added an extra condition to the edge case in
useFlowMeasureCalculationBool
What number of submissions are you getting on dev? I have:
- TrapVisit: 1
- TrapOps: 2
- FishProcess: 3
- FishIput: 4
- TrapPostProcessing: 5
Typing that out I just noticed the number of submissions is incrementing by 1. This might be a clue to what is causing this.
blocker or good to merge?
Completes #275, #267, #277 & #304.
hasSubmittedRef
ref inIncompleteSections
patches this to limit the final submission to one.setTimeout
introduced in theLoadingScreen
will need to be refactored in a future ticket.