New draft states for replay

[Sytten]

Summary of the gap

In the new release, each replay entry has a draft. This draft is kept even if you send the new version. This is different from previous Caido behaviour. The draft are keep backend and not lost between refresh.

What is the goal of this content?

Knowledge: An explanation of a concept or the 'why'.

Success Criteria

• Probably a knowledge to explain how the various concepts (collection, entries, draft) work together.
• Update the Task to match the new behaviour

Technical Details / Proposed Content

No response

See Also

No response

[Corb3nik]

@Sytten Why does the user need to know about this?

If a user has issues with drafts, this is a matter of having better UX. I don't think documentation will help with surprising/undesired behaviour.

@ninjeeter Lets wait before implement this.