Closing GNOME Builder when there are open files which have unreloaded external changes prompts you that there are unsaved changes
If an open file in Builder, e.g. a package.json file, is modified by an external program, e.g. npm, Builder will notify you that there are unsaved changes. While this sort of is true, I think it is counter-intuitive, and I wager that in most cases you are more interested in keeping the changes made by the external program than the buffer in Builder. That said, I'm not entirely sure what I'd consider the ideal solution here, but I find the current behaviour to be misleading.
- Open a project in Builder
- Open any given file in this project
- Modify this file in an external program and save it
- Note that Builder prompts you to reload the file as there have been external changes (don't reload it)
- Attempt to close Builder an be notified of "unsaved changes"
Builder version: 3.36.0 from Flathub