The types for `Permission` are not as in the API.
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 48/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Veraltet
- Tech-Stack
- typescript
- Bereich
- api
Rechercherichtung
Start by locating the beta Permission and SharePointIdentitySet type definitions, then compare grantedToV2 with the documented response and the reported Graph API response. Update the type to match the evidence and check the relevant generated or type validation tests; done means the definition accepts the reported grantedToV2 shape and remains consistent with the API documentation.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Describe the bug
The response for https://learn.microsoft.com/en-us/graph/api/filestoragecontainer-list-permissions?view=graph-rest-beta&tabs=http#response should be of type permission.
The type permission is described in the BETA package as:
export interface Permission extends Entity {
/**
* A format of yyyy-MM-ddTHH:mm:ssZ of DateTimeOffset indicates the expiration time of the permission. DateTime.MinValue
* indicates there's no expiration set for this permission. Optional.
*/
expirationDateTime?: NullableOption<string>;
// For user type permissions, the details of the users and applications for this permission. Read-only.
grantedTo?: NullableOption<IdentitySet>;
// For type permissions, the details of the users to whom permission was granted. Read-only.
grantedToIdentities?: NullableOption<IdentitySet[]>;
// For link type permissions, the details of the users to whom permission was granted. Read-only.
grantedToIdentitiesV2?: NullableOption<SharePointIdentitySet[]>;
// For user type permissions, the details of the users and applications for this permission. Read-only.
grantedToV2?: NullableOption<SharePointIdentitySet>;
/**
* Indicates whether the password is set for this permission. This property only appears in the response. Optional.
* Read-only. For OneDrive Personal only.
*/
hasPassword?: NullableOption<boolean>;
// Provides a reference to the ancestor of the current permission, if it's inherited from an ancestor. Read-only.
inheritedFrom?: NullableOption<ItemReference>;
// Details of any associated sharing invitation for this permission. Read-only.
invitation?: NullableOption<SharingInvitation>;
// Provides the link details of the current permission, if it's a link type permission. Read-only.
link?: NullableOption<SharingLink>;
// The type of permission, for example, read. See the Roles property values section for the full list of roles. Read-only.
roles?: NullableOption<string[]>;
// A unique token that can be used to access this shared item via the shares API. Read-only.
shareId?: NullableOption<string>;
}
As you can see, the value for grantedToV2 is an optional SharePointIdentitySet. That does neither match the response in the documentation (https://learn.microsoft.com/en-us/graph/api/filestoragecontainer-list-permissions?view=graph-rest-beta&tabs=http#response-1) nor the response I receive.
The response I receive is of the same structure as in the documentation. What I get as value on grantedToV2 rather reminds me of Person or User - it at least does have the property userPrincipalName.
Expected behavior
The types should match both the documentation and what I receive from the GraphAPI server.
How to reproduce
Download the types and try to match the response of the API request to the defined types.
SDK Version
0.43.0-preview
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
- Vorherrschende Sprache
- PowerShell
- Sterne
- 129
- Forks
- 35
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus microsoftgraph/msgraph-typescript-typings
-
status:waiting-for-triage type:bug
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
microsoftgraph/msgraph-typescript-typings#748 · 2 Reaktionen ·
-
status:waiting-for-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 48/100
-
status:waiting-for-triage type:feature
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 35/100
microsoftgraph/msgraph-typescript-typings#530 · 1 Reaktion ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 32/100
Alle Issues in microsoftgraph/msgraph-typescript-typings
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
fb55/htmlparser2#2579 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug good first issue needs-review
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
trycua/hermes-cua-spaces#17 ·
-
area/channels kind/bug priority/medium
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
nanocoai/nanoclaw#4501 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 69/100
AndyHazz/bookends.koplugin#134 ·