Skip to content

Fix User Application Role Connection endpoints#125

Merged
Exanlv merged 2 commits intodc-Ragnarok:masterfrom
PhaxeNor:master
Sep 2, 2025
Merged

Fix User Application Role Connection endpoints#125
Exanlv merged 2 commits intodc-Ragnarok:masterfrom
PhaxeNor:master

Conversation

@PhaxeNor
Copy link
Contributor

The user and application role connection needs to have a bind for ":applicationId" so added that, and change mapping to be correct for the data that is returned.

* Added applicationId paramter and binding
* Added required applicationId paramater and set bind
* Changed metadata type to optional object (as noted in Discord docs)
public ?string $platform_name;
public ?string $platform_username;
public ApplicationRoleConnectionMetadata $metadata;
public ?object $metadata;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason for this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Metadata is empty with ApplicationRoleConnectionMetadata because the response from the API that is for the user isn't of that format.

It returns an object with the metadata key names and their values.

String=>String|Int

The other method getRecords() does use ApplicationRoleConnectionMetadata but not this one.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll fix the mapping in a later release

@Exanlv Exanlv merged commit 5d3c19e into dc-Ragnarok:master Sep 2, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants