Can we make this behavior optional? Instead of always performing this action, we could introduce an alternative method or an additional argument in the copy method to allow developers to enable or disable it as needed.

@Llewellynvdm WordPress seems to be doing that. They have a separate function move_dir() which does the invalidation, while the base filesystem does not.

For me it's just a concern, that the Installer Adapters in Joomla do not seem to invalidate the opcache after copying the files through Folder::move().

Maybe an alternative would be just to use the File::copy method, i.e. instead of

                case 'file':
                    if ($useStreams) {
                        Stream::getStream()->copy($sfid, $dfid);
                    } else {
                        if (!@copy($sfid, $dfid)) {
                            throw new FilesystemException('Copy file failed', -1);
                        }
                        File::invalidateFileCache($dfid);
                    }

                    break;

use

                case 'file':
                    if (File::copy($sfid, $dfid, null, $useStreams) !== true) {
                        // File::copy throws an error
                        return false;
                    }

                    break;

We do similar already in the Folder::delete method where we call File::delete.

File::copy does also include the opcache invalidation, in opposite to this PR here also for the case if stream is used.

Thanks, I updated the PR. I wouldn't call File::copy, because it would cause quite a bit of overhead.