Closed cflipse closed 4 years ago
Why not redirect back to the new log form with a “save and add another” button or something? A few less clicks.
Possibly .... Although, I'm considering the idea that they'll be doing other things during the dive, and it won't just be table table table .... With checking on though
On Wed, Aug 14, 2019, 6:58 PM LizPrescott notifications@github.com wrote:
Why not redirect back to the new log form with a “save and add another” button or something? A few less clicks.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rubyforgood/coral/pull/66?email_source=notifications&email_token=AAAA5KQNZ4QW24VNFNQ3KF3QESE3DA5CNFSM4ILQL5P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4KLIKA#issuecomment-521450536, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAA5KUWZF77A2CS4TTV3BLQESE3DANCNFSM4ILQL5PQ .
Rework to allow a workflow loop while a dive is active:
From the dives page, you can create a new restoration log entry; the form will redirect you back to the active dive if present.
This allows creating multiple log entries, over and over, until marking the dive complete. It'd be good if we co8uld get the offline hookw working on this page, for that flow.