Description

POC on top of PR #37336

This PR demonstrates how we could catch an InvalidArgumentException thrown by setSharedWith if someone does an API call like:

curl --user jim:jim http://172.17.0.1:8080/ocs/v2.php/apps/files_sharing/api/v1/shares?format=json -d '{"shareType": 0, "shareWith": 256, "permissions": 31, "path": "/faaa"}' -X POST -H "Content-Type: application/json"
{"ocs":{"meta":{"status":"failure","statuscode":403,"message":"sharedWith is integer but must be a string","totalitems":"","itemsperpage":""},"data":[]}}

So they get a 403 and error message instead of a 500 with no message.

Related Issue

#37324

How Has This Been Tested?

Needs unit tests.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE