-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Save" in "Unsaved changes" doesn't do anything #1491
Comments
This seems to be fixed in 1.8.0. Although I don't know what your PR then maybe changed @giemic8? |
@freelon Are you sure? I can reproduce this Bug on 1.8.0 |
I will check again tomorrow on my work machine, where it worked last time with 1.8.0, but didn't with 1.7.1. Interestingly I just tried it out on my personal laptop (which runs the same OS) and I don't have the issue there even in 1.7.1. Could it have something to do with the collection involved, the kind of changes, or some dependency of the app that was updated in the meantime (bruno has 6 packages it depends on on Arch)? |
Possible duplicate of #1396 |
I just checked it again on my work machine (bruno 1.8.0) - it works @giemic8 |
I have to correct myself - now I do stumble upon the problem again in another request. One thing I was able to figure out what the difference might be: it works if requests without a BODY were changed. As soon as the request has a body (even if the change is in the URL), it's broken. |
@freelon The issue only exist if you have a json in the body. Maybe this hint will help you. |
Changing the state of the unsaved item back to the original saved state triggers the issue consistently for me. Steps to repro:
|
Bruno version: 1.7.1
Steps to reproduce:
... and nothing happens (bruno doesn't close either, which is a good thing). Only the "Don't save" and "Cancel" buttons do what they are supposed to do.
The text was updated successfully, but these errors were encountered: