Skip to content

types(GuildFeature): allow feature strings to be passed #8264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 17, 2022

Conversation

ImRodry
Copy link
Contributor

@ImRodry ImRodry commented Jul 10, 2022

Please describe the changes this PR makes and why it should be merged:

This PR fixes the type of all the props using the GuildFeature enum to allow feature strings to be passed along and not limit that to enum properties only. This is the only situation where raw data received from Discord is passed as it is, so using the feature strings is correct and safe. This also mimics the behavior in v13

Status and versioning classification:

  • Code changes have been tested against the Discord API, or there are no code changes
  • I know how to update typings and have done so, or typings don't need updating

Verified

This commit was signed with the committer’s verified signature.
ImRodry Rodrigo Leitão
Co-authored-by: Synbulat Biishev <syjalo.dev@gmail.com>
@vercel
Copy link

vercel bot commented Jul 10, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated
discord-js ⬜️ Ignored (Inspect) Jul 10, 2022 at 9:38PM (UTC)

@iCrawl iCrawl merged commit b7d4e55 into discordjs:main Jul 17, 2022
@ImRodry ImRodry deleted the types/allow-strings-guildfeature branch August 9, 2022 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

4 participants