Make sure to never trigger files hooks on a null path

[come-nc]

• Resolves: #34932

Summary

File pre/post operation events should only be triggered for files inside the default view. For other files a bogus event with a null path was fired, this avoids that.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• [x] Tests (unit, integration, api and/or acceptance) are included
• [x] Screenshots before/after for front-end changes
• [x] Documentation (manuals or wiki) has been updated or is not required
• [x] Backports requested where applicable (ex: critical bugfixes)

[come-nc]

• [x] Need https://github.com/nextcloud/server/pull/36836 first to avoid type errors

[tram98]

Thank you so much for the fix. I am really needing this fix because of issues with syncing bigger files.

[come-nc]

/rebase

[come-nc]

/rebase

[come-nc]

/rebase

[dinosmm]

Apologies for my lack of experience with GitHub and NC development, but will this only be pushed into Nextcloud 27 and not in a 26.0.x patch?

[susnux]

will this only be pushed into Nextcloud 27 and not in a 26.0.x patch?

Yes this will first be pushed into Nextcloud 27 and might then be backported to 26.0.x.

[solracsf]

@come-nc OK to be backported?

[come-nc]

Hum yeah psalm will complain about the backports I think because typing was hell, but let’s try it.

[come-nc]

/backport to stable26

[come-nc]

/backport to stable25