feature request: Make "Permissions" API objects consistent #16

New Issue

2026-02-16T12:28:58-05:00

yindo commented

2026-02-16 12:28:58 -05:00

Originally created by @QuantumToasted on GitHub (Nov 11, 2023).

What do you want to see?

There are multiple places in the API spec where an object representing a role's permissions (allowed and denied) is expressed, but I've noticed an inconsistency: Sometimes the fields are allow and deny (example: Set Role Permission), and sometimes they are a and d (example: Create Role). Could this be fixed up and unified in one way or another? It would make some API wrappers' lives easier not needing to include special JSON deserialization logic to handle the same model with differing field names, or having to include redundant model code. 😄

Originally created by @QuantumToasted on GitHub (Nov 11, 2023). ### What do you want to see? There are multiple places in the API spec where an object representing a role's permissions (allowed and denied) is expressed, but I've noticed an inconsistency: Sometimes the fields are `allow` and `deny` (example: [Set Role Permission](https://developers.revolt.chat/api/#tag/Server-Permissions/operation/roles_create_req)), and sometimes they are `a` and `d` (example: [Create Role](https://developers.revolt.chat/api/#tag/Server-Permissions/operation/roles_create_req)). Could this be fixed up and unified in one way or another? It would make some API wrappers' lives easier not needing to include special JSON deserialization logic to handle the same model with differing field names, or having to include redundant model code. 😄

yindo added the enhancement label 2026-02-16 12:28:58 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stoatchat/javascript-client-api#16