Broken requests sequence after any save or move existing requests #2573
Labels
bug
Something isn't working
Comments
Its-treason
added a commit
to Its-treason/bruno
that referenced
this issue
Jul 6, 2024
helloanoop
pushed a commit
that referenced
this issue
Jul 6, 2024
|
Thank you @Its-treason for the fix. I have merged the PR Will have a patch version 1.20.2 go out in the next few hours. |
|
This has been fixed in |
|
Confirm, just tested it. |
jwetzell
pushed a commit
to jwetzell/bruno
that referenced
this issue
Aug 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have checked the following:
Describe the bug
After 1.20.1 update was broken request sequences. On any save or move existing or new request value of "seq:" always sets on 1.
First image: before editing/create any request. Second image: i edited request that was on 7th place. It moved on 1st place.
Same happens if move any request, all them seq sets on 1.
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered: