Changes between Initial Version and Version 1 of Ticket #59196
- Timestamp:
- 08/24/2023 08:25:51 PM (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #59196 – Description
initial v1 1 In the wordpress-develop repo, I have a plugin file located in `src/wp-content/plugins/`. I've also initiated `npm run dev` (`grunt watch --dev`). I noticed in PhpStorm when editing the plugin file that often the editor complains about the file being modified on disk and whether I want to reload the file or use the copy in memory. What I think is happening is that the editor is I'll make a change and save and then I'll make another change . After the save, the `watch` command picks up on the change to the file and it is copying the file onto itself and thus bumping the modified time, causing the editor to detect a conflict. It turns out that this is not only the case for files in `src/wp-content/plugins` but all source files. It seems that `grunt watch` is erroneously copying source files onto itself when using the `--dev` option.1 In the wordpress-develop repo, I have a plugin file located in `src/wp-content/plugins/`. I've also initiated `npm run dev` (`grunt watch --dev`). I noticed in PhpStorm when editing the plugin file that often the editor complains about the file being modified on disk and whether I want to reload the file or use the copy in memory. What I think is happening is that the editor is I'll make a change and save and then I'll make another change and save again after a couple seconds. After the first save, the `watch` command picks up on the change to the file and it is copying the file onto itself and thus bumping the modified time, causing the editor to detect a conflict at the second save. It turns out that this is not only the case for files in `src/wp-content/plugins` but all source files. It seems that `grunt watch` is erroneously copying source files onto itself when using the `--dev` option.