refactor(graph): move "Invite" to new drive item permissions service

This introduces the new DriveItemPermissionsService and DriveItemPermissionsApi to
allow for better separation of the business logic and the API handling.

As a starting point the Invite method was moved to the new service. More to follow.
This commit is contained in:
Ralf Haferkamp
2024-03-25 18:14:16 +01:00
committed by Ralf Haferkamp
parent 531c926853
commit c6d28caa31
10 changed files with 623 additions and 541 deletions

View File

@@ -889,7 +889,7 @@ Feature: Send a sharing invitations
"code": {
"type": "string",
"enum": [
"generalException"
"invalidRequest"
]
},
"message": {
@@ -940,7 +940,7 @@ Feature: Send a sharing invitations
"properties": {
"code": {
"type": "string",
"pattern": "generalException"
"pattern": "invalidRequest"
},
"message": {
"type": "string",
@@ -1113,7 +1113,7 @@ Feature: Send a sharing invitations
"code": {
"type": "string",
"enum": [
"generalException"
"invalidRequest"
]
},
"message": {
@@ -1224,7 +1224,7 @@ Feature: Send a sharing invitations
"properties": {
"code": {
"type": "string",
"enum": ["generalException"]
"enum": ["invalidRequest"]
},
"message": {
"type": "string",
@@ -2375,14 +2375,14 @@ Feature: Send a sharing invitations
| sharee | grp1 |
| shareType | group |
| permissionsAction | <permissions-action> |
Then the HTTP status code should be "400"
Then the HTTP status code should be "400"
When user "Alice" sends the following share invitation using the Graph API:
| resource | FolderToShare |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsAction | <permissions-action> |
Then the HTTP status code should be "400"
Then the HTTP status code should be "400"
Examples:
| permissions-action |
| permissions/create |