api/graph: drop @access from enum values

The expectation with the @access directive is that permission
checks are automatically performed by core-go. However this is
actually a no-op for enum values.

Drop the enum value directives to make it clearer that permission
checks must be performed manually.
This commit is contained in:
Simon Ser 2023-08-18 10:47:30 +00:00 committed by Drew DeVault
parent 907fb2e104
commit 75d510d8f1
1 changed files with 4 additions and 4 deletions

View File

@ -43,7 +43,7 @@ read or write access. For the meta.sr.ht API, you have access to all public
information without any special permissions - user profile information,
public keys, and so on.
"""
directive @access(scope: AccessScope!, kind: AccessKind!) on FIELD_DEFINITION | ENUM_VALUE
directive @access(scope: AccessScope!, kind: AccessKind!) on FIELD_DEFINITION
enum Visibility {
"Visible to everyone, listed on your profile"
@ -121,9 +121,9 @@ type OAuthClient {
}
enum WebhookEvent {
PASTE_CREATED @access(scope: PASTES, kind: RO)
PASTE_UPDATED @access(scope: PASTES, kind: RO)
PASTE_DELETED @access(scope: PASTES, kind: RO)
PASTE_CREATED
PASTE_UPDATED
PASTE_DELETED
}
interface WebhookSubscription {