* Move unlock related tests from core to local api tests
* refactor tests
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
* test:add failing test to expected to failure
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
---------
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
* unifiedrole: Add CS3ResourcePermissionsToLibregraphActions
Add function to convert CS3ResourcePermsissions to libregraph actions
* unifiedrole: Fix strings for the UnifiedRoleConditionSelf
The "Self/Owner/Grantee" string are not part the the constraint value
* graph: Move getRoleDefinitionList to unifiedrole module
rename it to GetBuiltinRoleDefinitionList and make it public
* graph: turn libregraph resource actions into string constants
* graph/sharedbyme: Set the correct roles (or actions) on permissions
Try to map CS3 resource permissions on a share to one of the default libregraph
UnifiedRoleDefinitions. If a match if found return the roleid in 'permissions.roles'
attribute of the response. If no match if found convert the
ResourcePermissions in to `libre.graph.permissions.actions` and return
those in the response.
* Link the failing lock tests with correct issues that they are failing with
* Move locks relates tests to new suite
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
* address reviews
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
* Add new scenario for trying to lock a folder
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
---------
Signed-off-by: Swikriti Tripathi <swikriti808@gmail.com>
* bump reva to latest edge
To get https://github.com/cs3org/reva/pull/4336
* graph: Import unified role related code from reva
The UnifiedRole related types are pretty specific to the graph service.
Maintaining them as part of reva makes things more complex that required.
* chore: add failing cases to the expected failures
---------
Co-authored-by: Florian Schade <f.schade@icloud.com>
