Skip to content

Status posting Idempotency

Shpuld Shpludson requested to merge feat/idempotency into develop

Every time the currently composed status changes it updates the idempotency key with a timestamp, so it stays the same if the post status request fails, but changes every time user willingly changes the content in any way or the form is cleared after successful posting. Server won't let through statuses with the same idempotency key so this eliminates double posts when user thinks a status didn't go through and hits submit again without changes.

Merge request reports