Repository navigation
Add effective guild and channel permission endpoint constants - #34
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add GET endpoint constants for member and role permissions in guilds and channels, as proposed by discord/discord-api-docs#8695 at
9190695accc5eabecf7c6e2cd64fd3d583d9978c. The upstream documentation PR is still open; this does not establish live endpoint availability.Tests cover all four bindings, resource-based rate-limit keys, and explicit false query serialization. Replace an existing mock of the now-final React Promise Deferred with a real inert Deferred so the offline suite works with Promise 3. Prepare Http::VERSION for v10.9.9, which DiscordPHP needs before using these constants.
Validation: PHP 8.5 offline Discord suite: 31 tests, 221 assertions. Existing vendor deprecations were excluded from error reporting. Driver-server integration tests were not run; no transport behavior changes.