Reconsider the SEQ (sequence) property

[dse-copsfs]

Workflow

1. Add a new request in the existing folder of 10 requests at the second position.
2. All existing requests after the second position are modified because the seq property is incremented by one.
   

Idea

I think it's against the nice GIT-friendly approach – the change of one added file should not modify the rest of the existing files. Please reconsider the usage of the seq property.

What about to store sequence order info in separate file on the level of the concrete folder?

[end3rbyte]

I agree!